Bug 117502 - gcc: internal compiler error: Illegal instruction
Summary: gcc: internal compiler error: Illegal instruction
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: RC 1
Hardware: i686 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Michael Matz
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-16 17:25 UTC by James Ogley
Modified: 2005-10-06 16:03 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Ogley 2005-09-16 17:25:53 UTC
When building AbiWord 2.3.6 (although this has happened a number of times with
different things), the build died with:

In file included from /usr/include/stdio.h:72,
                 from pf_Frag.h:24,
                 from pf_Frag_Text.h:26,
                 from pf_Frag_Text.cpp:21:
/usr/include/libio.h:208: internal compiler error: Illegal instruction
Please submit a full bug report, with preprocessed source if appropriate.

For the preprocessed source, is that a tarball of the source tree as it stood
when the build failed?

Note that this happens on different header files each time, so I'm pretty sure
the problem isn't with libio.h, there also seems to be a correlation with the
temperature in the ACPI thermal zone being high, although that could simply be
because the temperature rises when the CPU is busy, which it is when it's
compiling something.
Comment 1 Michael Matz 2005-09-19 09:39:34 UTC
Are you saying that if you compile something multiple times with the exact 
same options, then it sometimes breaks and sometimes works?  In that case 
you just have a hardware problem.  Compiling something is CPU intensive so 
any hardware problem which might exist is possibly uncovered and hence 
you see it in the compiler.  You should run a memcheck when the machine 
is as hot as it is when compiling breaks, check your fans, especially the 
CPU ones or consider a BIOS update, if possible. 
Comment 2 Michael Matz 2005-10-06 16:03:34 UTC
No reaction, so this really seems to be a hardware problem.