Re: ICE during kernel compile [Re: mipsel buildd kernels]
Goswin von Brederlow wrote:
> Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> writes:
>
> > Goswin von Brederlow wrote:
> > [snip]
> > > Now I found ICE:
> > >
> > > gcc -D__KERNEL__ -I/home/mrvn/kernel/kernel-patch-2.4.25-mips-2.4.25/build-tmp/kernel-source-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I /home/mrvn/kernel/kernel-patch-2.4.25-mips-2.4.25/build-tmp/kernel-source-2.4.25/include/asm/gcc -G 0 -mno-abicalls -fno-pic -pipe -finline-limit=100000 -mabi=32 -march=mips32 -Wa,-32 -Wa,-march=mips32 -Wa,-mips32 -Wa,--trap -DMODULE -mlong-calls -DMODVERSIONS -include /home/mrvn/kernel/kernel-patch-2.4.25-mips-2.4.25/build-tmp/kernel-source-2.4.25/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=twofish -c -o twofish.o twofish.c
> > > gcc: Internal error: Killed (program cc1)
> > > Please submit a full bug report.
> > > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> > > For Debian GNU/Linux specific bugs,
> > > please see /usr/share/doc/debian/bug-reporting.txt.
> > >
> > > make[3]: *** [twofish.o] Error 1
> > > make[3]: Leaving directory `/home/mrvn/kernel/kernel-patch-2.4.25-mips-2.4.25/bu
> > > ild-tmp/kernel-source-2.4.25/crypto'
> > > make[2]: *** [_mod_crypto] Error 2
> >
> > Please report this bug against gcc, including the whole command line
> > used to invoke gcc, and the generated intermediate files
> > (via -save-temps), or a smaller testcase derived from those.
> >
> >
> > Thiemo
>
> I have a script that methodically tries to remove lines from C source and
> recompiles it over and over to minimise such ICE. Removals that make
> the compile fail or fix the ICE (any output without the ICE) get
> undone, removals that still ICE are kept.
That's a nice helper. :-) Trying that script on the preprocessed code
is probably the fastest method to find a good test case.
> But since I'm testbuilding the kernel-image debian package I haven't
> started that yet. The above problem could also just be an out of
> memory.
Not catching an OOM condition is still a bug.
> I only have 64MB and no swap so larger files can fail to build
> with no fault to gcc (usualy large C++ template riddled files but one
> never knows until one looks).
Gcc/g++ _should_ stop with an appropriate error message in that case.
Thiemo
Reply to: