gcc-2.95.2-51 is buggy
Quoted 2 lines
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
Yes, you are right.
So 2.95.2 fails for i386, i486, i586 and does not fail for i686.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · [email protected] wrote:
Quoted 3 lines
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
Yes, you are right.
So 2.95.2 fails for i386, i486, i586 and does not fail for i686.
RedHat 7.0's gcc 2.96 and kgcc do not seem to exhibit this problem:
me2v@reliant tmp $ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.0) me2v@reliant tmp $ kgcc -v
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) me2v@reliant tmp $ gcc -O2 -o bug bug.c ; ./bug0x0
me2v@reliant tmp $ gcc -o bug bug.c ; ./bug0x0
me2v@reliant tmp $ kgcc -O2 -o bug bug.c ; ./bug0x0
me2v@reliant tmp $ kgcc -o bug bug.c ; ./bug0x0
Signature · 11 lines
Matthew Vanecek perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);' ******************************************************************************** For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting in the way of something... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/