This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Why 2.0.34 compiles with gcc 2.8.* and egcs, whereas 2.0.33 will not , work properly
- To: egcs at cygnus dot com
- Subject: Why 2.0.34 compiles with gcc 2.8.* and egcs, whereas 2.0.33 will not , work properly
- From: "FireBird (Richard Rose)" <firebird at the-junction dot com>
- Date: Sat, 6 Jun 1998 13:59:28 +0100 (BST)
- Reply-To: "FireBird (Richard Rose)" <firebird at the-junction dot com>
Even though work is being done on the 2.1.* kernels, work is still
continuing on the 2.0.* kernels, (for now). This means that the latest
2.0.* kernel, which is 2.0.34, actually came out *after* the 2.1.40
kernel, so the bug was already found and fixed.
I'm sure the bug in question has been documentedm and can probably be
found on kernel.org, but I haven't tried to find it. The problem is that
linux/arch/<appropriate>/kernel/ioport.c gets partially optimized out,
breaking the socket layer of the kernel.
The general message is:
2.0.34 - Use any compiler
2.1.40 or higher - Use any compiler
2.0.33 or lower - get ioport.c from 2.0.40 or higher, then use any
compiler.
One last thing: I've just compiled egcs-1.0.3a. It works perfectly on my
i586-gnulibc1-pc. Keep up the good work.
Thanks
Richard Rose