From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andries.Brouwer@cwi.nl, jakub@redhat.com
Cc: alan@lxorguk.ukuu.org.uk, bernds@redhat.com, greg@linuxpower.cx,
linux-kernel@vger.kernel.org, torvalds@transmeta.com,
viro@math.psu.edu
Subject: Re: gcc-2.95.2-51 is buggy
Date: Fri, 24 Nov 2000 14:04:37 +0100 (MET) [thread overview]
Message-ID: <200011241304.OAA21196@harpo.it.uu.se> (raw)
On Fri, 24 Nov 2000, Jakub Jelinek wrote:
>so the reason why it did not show up in the gcc you picked up from
>ftp.gnu.org is that you have compiled it so that it defaults to -mcpu=i686
>where the bug does not show up.
Indeed. I just ran some tests, and I can confirm that gcc 2.95.2 vanilla
exhibits the bug when compiled and run for i486 or i585, but not i686.
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-24 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 13:04 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-27 14:28 Pavel Pisa;research student
2000-11-24 12:48 Andries.Brouwer
2000-11-24 16:46 ` Matthew Vanecek
2000-11-24 8:09 Frédéric L . W . Meunier
2000-11-24 5:20 Andries.Brouwer
2000-11-24 5:44 ` Neil Brown
2000-11-24 6:47 ` Alexander Viro
2000-11-25 17:26 ` Rik van Riel
2000-11-25 19:16 ` Jeff V. Merkey
2000-11-25 20:01 ` Andries Brouwer
2000-11-25 20:06 ` Rik van Riel
2000-11-26 15:33 ` Olaf Dietsche
2000-11-26 16:58 ` Rik van Riel
2000-11-26 19:36 ` Mike Castle
2000-11-26 19:41 ` Russell King
2000-11-26 19:55 ` J . A . Magallon
2000-11-24 9:37 ` Ion Badulescu
2000-11-24 10:18 ` Linux Kernel Developer
2000-11-24 9:57 ` Jakub Jelinek
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=200011241304.OAA21196@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bernds@redhat.com \
--cc=greg@linuxpower.cx \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®