public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: scott douglass <sdouglass@arm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/7093: ICE building libgcc during boostrap Date: Thu, 08 May 2003 12:16:00 -0000 [thread overview] Message-ID: <20030508121600.12785.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/7093; it has been noted by GNATS. From: scott douglass <sdouglass@arm.com> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, dhazeghi@yahoo.com, giovannibajo@libero.it Cc: Subject: Re: bootstrap/7093: ICE building libgcc during boostrap Date: Thu, 08 May 2003 13:15:09 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7093 Dara Hazeghi <dhazeghi@yahoo.com> wrote: > could the submitter of this bug please enclose the preprocessed source > that is crashing the compiler build, or test to see whether this bug > occurs in a more current version (ie 3.2.3). We have number of reports > of successful builds on hppa2.0w-hp-hpux11.00, so it seems likely that > the bug has been fixed. I have retried with 3.2.3 and I still get the same result. [...] ./xgcc -B./ -B/home/sdouglas/tools/GNU/gcc/3_2_3/hpux_11-hppa2_0w/hppa2.0w-hp-hpux11.00/bin/ -isystem /home/sdouglas/tools/GNU/gcc/3_2_3/hpux_11-hppa2_0w/hppa2.0w-hp-hpux11.00/include -isystem /home/sdouglas/tools/GNU/gcc/3_2_3/hpux_11-hppa2_0w/hppa2.0w-hp-hpux11.00/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../src-hpux_11-hppa2_0w/gcc -I../../src-hpux_11-hppa2_0w/gcc/. -I.. /../src-hpux_11-hppa2_0w/gcc/config -I../../src-hpux_11-hppa2_0w/gcc/../include -DL_muldi3 -c ../../src-hpux_11-hppa2_0w/gcc/libgcc2.c -o libgcc/./_muldi3.o ../../src-hpux_11-hppa2_0w/gcc/libgcc2.c:0: Internal compiler error in default_no_named_section, at varasm.c:5305 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. make[3]: *** [libgcc/./_muldi3.o] Error 1 make[3]: Leaving directory `/tmp_mnt/home/sdouglas/gnu/builds/gcc-3.2.3/build-hpux_11-hppa2_0w/gcc' make[2]: *** [libgcc.a] Error 2 make[2]: Leaving directory `/tmp_mnt/home/sdouglas/gnu/builds/gcc-3.2.3/build-hpux_11-hppa2_0w/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/tmp_mnt/home/sdouglas/gnu/builds/gcc-3.2.3/build-hpux_11-hppa2_0w/gcc' make: *** [bootstrap-lean] Error 2 Contrary to my original guess in this PR, I now believe that configuring using '--with-dwarf2' *is* required to provoke the problem. Here's my configure command: ../src-hpux_11-hppa2_0w/configure \ --prefix=/home/sdouglas/tools/GNU/gcc/3_2_3 \ --exec-prefix=/home/sdouglas/tools/GNU/gcc/3_2_3/hpux_11-hppa2_0w \ --program-suffix=-3_2_3 \ -v --with-dwarf2 --enable-version-specific-runtime-libs --with-gnu-as --with-as=/home/sdouglas/tools/GNU/binutils/2_13_2_1/hpux_11-hppa2_0w/bin/as-2_13_2_1 Here's my make command: make STAGE1_CFLAGS=-O2 BOOT_CFLAGS=-O2 MAKE=make bootstrap-lean I can supply pre-processed source -- but the problem may well require that the xgcc has been built with --with-dwarf2. Let me know if you'd like pre-processed source and where to send it to.
next reply other threads:[~2003-05-08 12:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-08 12:16 scott douglass [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-09 8:16 scott douglass 2003-05-08 10:44 giovannibajo 2003-05-08 4:06 Dara Hazeghi 2002-06-21 1:26 sdouglass
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=20030508121600.12785.qmail@sources.redhat.com \ --to=sdouglass@arm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).