From: Jakub Jelinek <jakub@redhat.com>
To: Andries.Brouwer@cwi.nl
Cc: greg@linuxpower.cx, viro@math.psu.edu, alan@lxorguk.ukuu.org.uk,
bernds@redhat.com, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: gcc-2.95.2-51 is buggy
Date: Fri, 24 Nov 2000 04:57:02 -0500 [thread overview]
Message-ID: <20001124045702.M1514@devserv.devel.redhat.com> (raw)
In-Reply-To: <UTC200011240520.GAA143373.aeb@aak.cwi.nl>
In-Reply-To: <UTC200011240520.GAA143373.aeb@aak.cwi.nl>; from Andries.Brouwer@cwi.nl on Fri, Nov 24, 2000 at 06:20:33AM +0100
On Fri, Nov 24, 2000 at 06:20:33AM +0100, Andries.Brouwer@cwi.nl wrote:
> >> ... RedHat's GCC snapshot "2.96" handles this case just fine.
>
> > Now, if you can isolate the relevant part of the diff between
> > 2.95.2 and RH 2.96...
>
> Maybe I have to be more precise in the statement "gcc 2.95.2 is buggy".
>
> I just installed gcc 2.95.2 freshly ftp'ed from ftp.gnu.org, and
>
> % /usr/bin/gcc -v
> Reading specs from /usr/lib/gcc-lib/i486-suse-linux/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> % /usr/bin/gcc -Wall -O2 -o bug bug.c; ./bug
> 0x84800000
> % /usr/gcc/aeb/bin/gcc -v
> Reading specs from /usr/gcc/aeb/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> % /usr/gcc/aeb/bin/gcc -Wall -O2 -o nobug bug.c; ./nobug
> 0x0
>
> So, not all versions of gcc 2.95.2 are equal.
I believe all 2.95.2's are equal in this, I think the fact that it gives 0
in the nobug case is some other reason:
$ for i in gcc kgcc '/usr/src/gcc-trunk/obj/gcc/xgcc -B /usr/src/gcc-trunk/obj/gcc/' '/usr/src/gcc-2.95.2/obj/gcc/xgcc -B /usr/src/gcc-2.95.2/obj/gcc/'; do $i -v; for j in -mcpu=i386 -mcpu=i586 -mcpu=i686; do $i $j -O2 -o aeb aeb.c; echo -n "$i $j "; ./aeb; done; done
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.0)
gcc -mcpu=i386 0x0
gcc -mcpu=i586 0x0
gcc -mcpu=i686 0x0
Reading specs from /usr/lib/gcc-lib/i386-glibc21-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
kgcc -mcpu=i386 0x0
kgcc -mcpu=i586 0x0
kgcc -mcpu=i686 0x0
Reading specs from /usr/src/gcc-trunk/obj/gcc/specs
Configured with:
gcc version 2.97 20001120 (experimental)
/usr/src/gcc-trunk/obj/gcc/xgcc -B /usr/src/gcc-trunk/obj/gcc/ -mcpu=i386 0x0
/usr/src/gcc-trunk/obj/gcc/xgcc -B /usr/src/gcc-trunk/obj/gcc/ -mcpu=i586 0x0
/usr/src/gcc-trunk/obj/gcc/xgcc -B /usr/src/gcc-trunk/obj/gcc/ -mcpu=i686 0x0
Reading specs from /usr/src/gcc-2.95.2/obj/gcc/specs
gcc version 2.95.2 19991024 (release)
/usr/src/gcc-2.95.2/obj/gcc/xgcc -B /usr/src/gcc-2.95.2/obj/gcc/ -mcpu=i386 0x84800000
/usr/src/gcc-2.95.2/obj/gcc/xgcc -B /usr/src/gcc-2.95.2/obj/gcc/ -mcpu=i586 0x84800000
/usr/src/gcc-2.95.2/obj/gcc/xgcc -B /usr/src/gcc-2.95.2/obj/gcc/ -mcpu=i686 0x0
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.
Jakub
-
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 prev parent reply other threads:[~2000-11-24 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 5:20 gcc-2.95.2-51 is buggy 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-24 8:09 Frédéric L . W . Meunier
2000-11-24 12:48 Andries.Brouwer
2000-11-24 16:46 ` Matthew Vanecek
2000-11-24 13:04 Mikael Pettersson
2000-11-27 14:28 Pavel Pisa;research student
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=20001124045702.M1514@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bernds@redhat.com \
--cc=greg@linuxpower.cx \
--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