unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: libgd security update / i686 issues
Date: Thu, 28 Jul 2016 13:22:40 -0400	[thread overview]
Message-ID: <877fc5n0db.fsf@netris.org> (raw)
In-Reply-To: <20160728163027.GA10649@jasmine> (Leo Famulari's message of "Thu, 28 Jul 2016 12:30:28 -0400")

Leo Famulari <leo@famulari.name> writes:

> On Thu, Jul 28, 2016 at 10:40:49AM +0200, Andreas Enge wrote:
>> Well, the bug report states that the result is correct on armv7. Apparently
>> i686 is not IEEE compliant by default, while armv7 is. So it should be okay
>> to apply the flags only on i686. We assume that SSE, but not SSE2 or later
>> are supported, see our Qt package.
>
> Thanks for the advice. What do you think about the attached patch?

Not all i686 systems have support for SSE.  I don't think we should
apply the upstream suggested workaround, which effectively amounts to
dropping support for older systems.  If we want to add a requirement for
SSE for i686 systems in Guix, that should be a separate discussion, and
not rushed in as part of a security update.

I will adapt my patch to the new version.

     Mark

  reply	other threads:[~2016-07-28 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  7:23 libgd security update / i686 issues Leo Famulari
2016-07-28  8:34 ` Andreas Enge
2016-07-28  8:40 ` Andreas Enge
2016-07-28 16:30   ` Leo Famulari
2016-07-28 17:22     ` Mark H Weaver [this message]
2016-07-28 18:38       ` Leo Famulari
2016-07-28 18:56       ` Leo Famulari
2016-07-28 20:47         ` Leo Famulari
2016-07-29 17:59         ` Mark H Weaver
2016-07-29 18:52           ` Leo Famulari
2016-07-29 20:33           ` Mark H Weaver
2016-07-28 21:26 ` Leo Famulari
2016-07-29 15:00   ` Ludovic Courtès
2016-07-29 15:42     ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877fc5n0db.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).