All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
	xiyou.wangcong@gmail.com, goodmenkernel@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: Is there any word about this bug in gcc ?
Date: Mon, 19 Nov 2007 22:47:59 -0800	[thread overview]
Message-ID: <4742831F.9040408@zytor.com> (raw)
In-Reply-To: <E1IuMnZ-0003o3-00@gondolin.me.apana.org.au>

Herbert Xu wrote:
> David Miller <davem@davemloft.net> wrote:
>> Because the compiler knows things about the inputs and can
>> thus apply optimizations that a static implementation in glibc
>> that has to handle all forms of inputs cannot.
> 
> On an unrelated note, I wonder if distros will be treating this
> with the same level of urgency as security vulnerabilities,
> especially in light of Shamir's recent note on maths errors.
> 

This one is definitely messy.  There is absolutely no way to know what 
gcc has miscompiled.  It looks to me that both gcc 4.2 and 4.3 are 
affected, any others?

	-hpa

  reply	other threads:[~2007-11-20  6:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  2:13 Is there any word about this bug in gcc ? zhengyi
2007-11-20  4:16 ` WANG Cong
2007-11-20  5:10   ` H. Peter Anvin
2007-11-20  5:39     ` WANG Cong
2007-11-20  6:03       ` Li Zefan
2007-11-20  6:10         ` WANG Cong
2007-11-20  6:04       ` H. Peter Anvin
2007-11-20  6:17       ` David Miller
2007-11-20  6:41         ` Herbert Xu
2007-11-20  6:47           ` H. Peter Anvin [this message]
2007-11-20  6:52             ` Herbert Xu
2007-11-20 12:52               ` Alessandro Suardi
2007-11-20 18:42                 ` Sami Farin
2007-11-20 21:10             ` Nix
2007-11-21 13:16               ` Alexander E. Patrakov
2007-11-21 16:19                 ` Alexander E. Patrakov
2007-11-21 17:22                   ` Lennart Sorensen

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

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

  git send-email \
    --in-reply-to=4742831F.9040408@zytor.com \
    --to=hpa@zytor.com \
    --cc=davem@davemloft.net \
    --cc=goodmenkernel@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.