From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jakub@redhat.com, David <dllorens@lsi.uji.es>,
linux-kernel@vger.kernel.org
Subject: Re: Posible bug in gcc
Date: Mon, 26 Feb 2001 13:02:45 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.1010226130127.5731A-100000@chaos.analogic.com> (raw)
In-Reply-To: <E14XRyY-0001gE-00@the-village.bc.nu>
On Mon, 26 Feb 2001, Alan Cox wrote:
> > > Well gcc-bugs would be the better place to send it but this is a known problem
> > > fixed in CVS gcc 2.95.3, CVS gcc 3.0 branch and gcc 2.96 (unofficial, Red Hat)
> >
> > I'm not sure if it is known, at least not known to me, but definitely not
> > fixed in any of gcc 2.95.2, CVS gcc 3.0 branch, CVS gcc 3.1 head, gcc 2.96-RH.
>
> Sorry my error for assuming it was the exsting known strength reduce bug
>
Script started on Mon Feb 26 12:54:20 2001
# gcc -o xxx bug.c
# ./xxx
Correct output: 5 2
GCC output: 5 2
# gcc --version
egcs-2.91.66
# gcc -O2 -o xxx bug.c
# ./xxx
Correct output: 5 2
GCC output: 10 5
# exit
exit
Script done on Mon Feb 26 12:55:21 2001
Definitely has something to do with broken optimization. No optimization,
no bug, turn on '-O2' and you have the bug.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
next prev parent reply other threads:[~2001-02-26 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 16:30 Posible bug in gcc David
2001-02-26 17:15 ` Alan Cox
2001-02-26 17:33 ` Jakub Jelinek
2001-02-26 18:02 ` Alan Cox
2001-02-26 18:02 ` Richard B. Johnson [this message]
2001-02-27 19:50 ` Ville Herva
2001-02-26 21:03 ` J . A . Magallon
2001-02-26 20:53 ` David Relson
2001-02-26 22:30 ` J . A . Magallon
2001-02-27 10:56 ` Erik Mouw
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=Pine.LNX.3.95.1010226130127.5731A-100000@chaos.analogic.com \
--to=root@chaos.analogic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dllorens@lsi.uji.es \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).