Re: GCC 4.4.x on HPUX 11.00 PA-RISC

[Ian Lance Taylor <iant at google dot com>]

Phezzan <phezzan0@gmail.com> writes:

> I'm trying to build GCC 4.4.0 on HPUX 11.00 using a GCC 3.2 binary
> built by a third party.
> I get the same error with 4.4.2.
>
> I've run into and worked around a few problems - the most significant
> being an assembler problem
> "Error: Field out of range" while compiling fold-const.c which I
> worked around by forcing -O2 into CFLAGS for the gcc Makefile
>
> I'm stuck in libgcc - specifically using xgcc to build libgcc2.c - I get this:
> /home/install/gcc/gcc-4.4.0/libgcc/../gcc/libgcc2.c: In function '__clzdi2':
> /home/install/gcc/gcc-4.4.0/libgcc/../gcc/libgcc2.c:735: internal
> compiler error: Segmentation fault
> Please submit a full bug report,
>
> I have no idea how to deal with this...  here's the command line it's
> running that fails:
>
> /home/install/gcc/build-gcc-4.4.0/./gcc/xgcc
> -B/home/install/gcc/build-gcc-4.4.0/./gcc/
> -B/usr/gcc-4.4.0/hppa2.0w-hp-hpux11.00/bin/
> -B/usr/gcc-4.4.0/hppa2.0w-hp-hpux11.00/lib/ -isystem
> /usr/gcc-4.4.0/hppa2.0w-hp-hpux11.00/include -isystem
> /usr/gcc-4.4.0/hppa2.0w-hp-hpux11.00/sys-include -g -O2 -O2   -DIN_GCC
>   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -Wcast-qual -Wold-style-definition  -isystem ./include  -fPIC -g
> -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I. -I.
> -I../.././gcc -I/home/install/gcc/gcc-4.4.0/libgcc
> -I/home/install/gcc/gcc-4.4.0/libgcc/.
> -I/home/install/gcc/gcc-4.4.0/libgcc/../gcc
> -I/home/install/gcc/gcc-4.4.0/libgcc/../include  -DHAVE_CC_TLS -o
> _clzdi2.o -MT _clzdi2.o -MD -MP -MF _clzdi2.dep -DL_clzdi2 -c
> /home/install/gcc/gcc-4.4.0/libgcc/../gcc/libgcc2.c \


This looks like a bug in the compiler.  If this is happening in the
first stage, then it may be a bug in the compiler you are using to do
the stage 1 build--i.e., gcc 3.2.  In that case, you should use -O2
only for fold-const.c, and not for any other file.  If that doesn't
help, then unfortunately I don't have any suggestion other than to
file a bug report as described at http://gcc.gnu.org/bugs.html .

Ian