Bug 24641 - GCC 2.96 Internal error when compiling UPX 1.04
GCC 2.96 Internal error when compiling UPX 1.04
Product: Red Hat Raw Hide
Classification: Retired
Component: gcc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-01-22 15:16 EST by bruns
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-28 10:02:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bruns 2001-01-22 15:16:18 EST
gcc  -DWITH_UCL '-DUPX_CONFIG_H="config_h/linux.h"' -I. -I/usr/src/u/ucl-0.92/include -Werror -O6 -mpentiumpro -march=pentiumpro 
-march=i386 -mcpu=pentium -Wsynth -fconserve-space -fno-exceptions -fno-rtti -o c_init.o -c c_init.cpp
c_init.cpp: In function `int set_fg (FILE *, int)':
c_init.cpp:111: Internal compiler error in emit_move_insn_1, at expr.c:
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make: *** [c_init.o] Error 1

C++ Bomb.
Not much else to say for this one.  This is the standard UPX and UCL code at http://upx.tsx.org. If you want to do specific things, drop me an 
e-mail and I will give it a go...


Linux kernel 2.4.0 with International patches
Hand compiled latest glibc CVS tree (glibc 2.2.1)
256 Megs of RAM on a Dual Proc PII 333.
Comment 1 Jakub Jelinek 2001-01-23 04:52:54 EST
Can you please run
gcc  -DWITH_UCL '-DUPX_CONFIG_H="config_h/linux.h"' -I. -I/usr/src/u/ucl-0.92/include -Werror -O6 -mpentiumpro -march=pentiumpro
-march=i386 -mcpu=pentium -Wsynth -fconserve-space -fno-exceptions -fno-rtti -o c_init.o -c c_init.cpp -save-temps -v
and attach here c_init.ii this generates. ICEs are often dependant on the exact
content of all the headers which come into the game and preprocessing the source
is the easiest way how to make sure we're looking at the same thing.
Comment 2 bruns 2001-01-23 13:54:48 EST
Alright, file generated.  But due to the fact I dont see any way to attach a file here (I may be blind and its sitting right in front of my face), I threw it up on 
my web server, URL is as follows.

Comment 3 Jakub Jelinek 2001-01-28 10:02:21 EST
I've commited a fix for this to CVS gcc and the patch will appear
in gcc-c++-2.96-73.
See http://gcc.gnu.org/ml/gcc-patches/2001-01/msg02070.html
Comment 4 Jakub Jelinek 2001-02-05 16:05:17 EST
Fix is in 2.96-73 and above (currently -74).

Note You need to log in before you can comment on or make changes to this bug.