Bug 12835 - internal compiler error: Illegal instruction
Summary: internal compiler error: Illegal instruction
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: c (show other bugs)
Version: 3.3.1
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: ice-on-valid-code
Depends on:
Blocks:
 
Reported: 2003-10-30 02:26 UTC by Peter Haight
Modified: 2003-11-02 19:27 UTC (History)
1 user (show)

See Also:
Host: i686-pc-freebsd5.1
Target: i686-pc-freebsd5.1
Build: i686-pc-freebsd5.1
Known to work:
Known to fail:
Last reconfirmed: 2003-10-30 04:10:21


Attachments
preprocced file that causes internal error (15.74 KB, text/plain)
2003-10-30 02:28 UTC, Peter Haight
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Haight 2003-10-30 02:26:20 UTC
Trying to compile xlife from ports/games/xlife gave me this error:

button.c:97: internal compiler error: Illegal instruction

It seems to work ok if I remove the -O from the command-line.

GCC:
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.3.1 [FreeBSD]

System:
FreeBSD 5.1-CURRENT (From CVS 9/21/03)

Options:
Whatever the standard gcc building options were for FreeBSD.

Command-Line:
cc -O  -pipe -mcpu=pentiumpro -mcpu=pentiumpro     -I/usr/X11R6/include   
-DCSRG_BASED  -DFUNCPROTO=15 -DNARROWPROTO    -DDIR=\"/usr/X11R6/lib/X11/xlife\"
-c button.c

Compiler Output:
button.c: In function `Button':
button.c:97: internal compiler error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

Preprocessed File:
(I'll add an attachment).
Comment 1 Peter Haight 2003-10-30 02:28:03 UTC
Created attachment 5019 [details]
preprocced file that causes internal error
Comment 2 Andrew Pinski 2003-10-30 04:10:17 UTC
I cannot reproduce it, are you sure that your memory is not bad?
Comment 3 Andrew Pinski 2003-10-30 04:10:30 UTC
I cannot reproduce it, are you sure that your memory is not bad?
Comment 4 Peter Haight 2003-11-02 19:19:10 UTC
I'm pretty sure it was a hardware problem now. Even if I rebooted and did some
of the tests mentioned on the SIG11 page (http://www.bitwizard.nl/sig11/), it
would always die in the same place. But that doc did suggest that you can have
problems if you IDE cable is too long and I had just installed a new drive with
a longer IDE cable. I switched back to the old cable and I'm not getting the
compiler error anymore.
Comment 5 Falk Hueffner 2003-11-02 19:27:42 UTC
Let's close it, then.