public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ahs3@fc.hp.com To: gcc-gnats@gcc.gnu.org Cc: ahs3@fc.hp.com Subject: other/8261: internal error when trying to build hpux cross compiler Date: Thu, 17 Oct 2002 10:16:00 -0000 [thread overview] Message-ID: <20021017170826.9D48ADB995@fcahs3.fc.hp.com> (raw) >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:
next reply other threads:[~2002-10-17 17:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-17 10:16 ahs3 [this message] 2003-05-07 8:56 Dara Hazeghi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021017170826.9D48ADB995@fcahs3.fc.hp.com \ --to=ahs3@fc.hp.com \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).