Messages in this thread |  | | Date | Fri, 24 Nov 2000 06:09:42 -0200 | From | Frédéric L . W . Meunier <> | Subject | Re: gcc-2.95.2-51 is buggy |
| |
Andries.Brouwer@cwi.nl wrote:
<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/
|  |