Re: other/8261: internal error when trying to build hpux cross compiler

Re: other/8261: internal error when trying to build hpux cross compiler

[Dara Hazeghi]

The following reply was made to PR other/8261; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
   ahs3@fc.hp.com
Cc:  
Subject: Re: other/8261: internal error when trying to build hpux cross compiler
Date: Wed, 7 May 2003 01:48:06 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=8261
 
 Hello,
 
 could the submitter please confirm whether this problem still occurs in  
 gcc 3.2.3? If so, would it be possible to include the preprocessed  
 source that the compiler is crashing on (as indicated in the error  
 message), so that we may check whether this bug exists in newer  
 versions of gcc? Thanks,
 
 Dara
 

other/8261: internal error when trying to build hpux cross compiler

[ahs3]

>Number:         8261
>Category:       other
>Synopsis:       internal error when trying to build hpux cross compiler
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 17 10:16:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Al Stone
>Release:        3.2
>Organization:
Hewlett-Packard
>Environment:
System: Linux fcahs3 2.4.18-ac3 #6 Thu Oct 10 11:54:16 MDT 2002 i686 unknown unknown GNU/Linux
Architecture: i686
host: i686-pc-linux-gnu
build: ia64-hp-hpux11.22
target: ia64-hp-hpux11.22
configured with:  used the following script to build....
   #!/bin/sh
   #
   #   Build cross-compiler for ia64 running hpux
   #
   
   GCC_SRC=gcc-3.2
   GCC_BLD=ia64-gcc-hpux
   
   PREFIX=/opt/ia64-hpux
   EXEC_PREFIX=${PREFIX}/bin
   
   TARGET=ia64-hp-hpux11.22
   HEADERS=../hpux-include
   
   cd /home/ahs3/projects/martin/gcc
   rm -rf $GCC_BLD
   
   #-- build gcc next
   echo "============ GCC ====================="
   [ -d $GCC_BLD ] || mkdir $GCC_BLD
   cd $GCC_BLD
   [ -f Makefile ] && make clean
   
   export PATH=$PATH:$EXEC_PREFIX
   
   CCOPTS=-Wall \
   AS_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-as         \
      LD_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-ld         \
      AR_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-ar         \
      RANLIB_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-ranlib \
      NM_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-nm         \
      OBJDUMP_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-objdump \
      ../$GCC_SRC/configure --enable-languages=c \
         --target $TARGET --prefix=$PREFIX -v --enable-threads=posix \
         --with-headers=${HEADERS}
   [ $? = 0 ] || exit 1
   
   CCOPTS=-Wall \
   AS_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-as         \
      LD_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-ld         \
      AR_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-ar         \
      NM_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-nm         \
      OBJDUMP_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-objdump \
      RANLIB_FOR_TARGET=${EXEC_PREFIX}/${TARGET}-ranlib \
      make all install
   [ $? = 0 ] || exit 1
   
   exit 0
   
>Description:
	When trying to build a cross-compiler (from Debian GNU/Linux 3.0,
	to HP-UX 11.22, I get the following internal error when the compiler
	tries to build itself:
	../../gcc-3.2/gcc/config/ia64/unwind-ia64.c: In function `alloc_reg_state':
	../../gcc-3.2/gcc/config/ia64/unwind-ia64.c:263: Internal compiler error in emit_move_insn, at expr.c:2776
	
>How-To-Repeat:
	Build binutils using the target and prefix values from the script listed
	in "configure with".  Then, build gcc using the script in the "configure
	with" field.  The ICE occurs when trying to compile the file gcc/
	config/ia64/unwind-ia64.c.  At least, that's what I did.  It appears
	that binutils is not involved in this particular problem, though it
	is needed to get this far in the build.
>Fix:
	No known workaround.  I tried several attempts to rewrite the code
	that causes the internal compiler error (in ia64intrin.c and in
	unwind-ia64.c) but made no progress.
>Release-Note:
>Audit-Trail:
>Unformatted: