Re: [Re: gcc: internal compiler error: program cc1 got fatal signal 11]

Jesse Pollard (pollard@tomcat.admin.navo.hpc.mil)
Fri, 29 Jun 2001 07:48:47 -0500 (CDT)


>
>
> "This is almost always the result of flakiness in your hardware - either
> RAM (most likely), or motherboard (less likely). "
>
> I cannot understand this. There are many other
> stuffs that I compiled with gcc without any problem. Again compilation is only
> a application. It only parse and gernerates object files. How can RAM or
> motherboard makes different

It's most likely flackey memory.

Remember- a single bit that dropps can cause the signal 11. It doesn't have
to happen consistently either. I had the same problem until I slowed down
memory access (that seemd to cover the borderline chip).

The compiler uses different amounts of memory depending on the source file,
number of symbols defined (via include headers). When the multiple passes
occur simultaneously, there is higher memory pressure, and more of the
free space used. One of the pages may flake out. Compiling the kernel
puts more pressure on memory than compiling most applications.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/