Re: gcc-2.95.2-51 is buggy

From: Frédéric L . W . Meunier (0@pervalidus.net)
Date: Fri Nov 24 2000 - 03:09:42 EST

Next message: Ulrich Windl: "2.2.16: How to freeze the kernel"
Previous message: Boszormenyi Zoltan: "Jens Axboe's blk-11 causing problems"
Maybe in reply to: Andries.Brouwer@cwi.nl: "gcc-2.95.2-51 is buggy"
Next in thread: Ion Badulescu: "Re: gcc-2.95.2-51 is buggy"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

<skip>
> % /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)gcc version 2.95.2 19991024 (release)
> % /usr/gcc/aeb/bin/gcc -Wall -O2 -o nobug bug.c; ./nobug
> 0x0

Interesting. On a Slackware 7.1 recently upgraded to glibc 2.2
(and where gcc 2.95.2 from ftp.gnu.org was built because 2.2
requires this version) I get:

% gcc -Wall -O2 -o bug bug.c
% ./bug
0x84800000

% egcs-2.91.66 -Wall -O2 -o bug bug.c
% ./bug
0x0

% gcc -Wall -O -o bug bug.c
% ./bug
0x0

% gcc -v
Reading specs from
/usr/lib/gcc-lib/i386-slackware-linux/2.95.2/specs
gcc version 2.95.2 19991024 (release)

% egcs-2.91.66 -v
Reading specs from
/usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)

Slackware's -current tree was upgraded to glibc 2.2 and gcc
2.95.2, but I built them myself.

-- 
0@pervalidus.{net, com, dyndns.org}
-
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 message: Ulrich Windl: "2.2.16: How to freeze the kernel"
Previous message: Boszormenyi Zoltan: "Jens Axboe's blk-11 causing problems"
Maybe in reply to: Andries.Brouwer@cwi.nl: "gcc-2.95.2-51 is buggy"
Next in thread: Ion Badulescu: "Re: gcc-2.95.2-51 is buggy"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Nov 30 2000 - 21:00:11 EST