Re: [Laptopkernel-devel] non-compile problem with gcc 3.3

[Anders Karlsson]

Morning,

On Fri, 2003-05-30 at 13:02, Jochen Michel wrote:
> I installed GCC 3.3 final packages from
> .../people/pthomas/gcc/3.3/8.2-i386/ on my SuSE 8.2 Pro. Compiling
> 2.4.21-rc4 works, with laptopkernel patch applied I still get:
> 
> make[2]: Entering directory `/usr/src/linux-2.4.21-rc4/kernel'
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.21-rc4/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=pentium4
>   -nostdinc -iwithprefix include -DKBUILD_BASENAME=sched
> -fno-omit-frame-pointer -c -o sched.o sched.c
> sched.c: In function `schedule':
> sched.c:709: internal compiler error: in merge_assigned_reloads, at
> reload1.c:6134
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> make[2]: *** [sched.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.4.21-rc4/kernel'
> make[1]: *** [first_rule] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.21-rc4/kernel'
> make: *** [_dir_kernel] Error 2
> 
> 
> Apparently there is some code from laptopkernel patch which does'nt
> comply to the strict gcc 3.3 rules. SwSusp? Acpi?

I thought there was someone that figured out that it was swsusp that
modified the file that breaks gcc. You might want to report back to the
gcc team that the compiler breaks on the code and you might also want to
let the swsusp team know that. Either team might have a work-around
available for the compiler you are using.

Either way, the right answer it to get things working with gcc 3.3 as
that compiler is not going to go away, quite the opposite. :)

Anyone disagree?


Regards,

-- 
Anders Karlsson <address@hidden>
Trudheim Technology Limited

signature.asc
Description: This is a digitally signed message part