public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Panagiotis Issaris <panagiotis.issaris@mech.kuleuven.ac.be> To: gcc-gnats@gcc.gnu.org Subject: bootstrap/7635: GCC 3.2 crashes during GCC 3.2 compilation Date: Mon, 19 Aug 2002 10:46:00 -0000 [thread overview] Message-ID: <1029772142.24540.155.camel@takis> (raw) >Number: 7635 >Category: bootstrap >Synopsis: GCC 3.2 crashes during GCC 3.2 compilation >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Mon Aug 19 08:56:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Panagiotis Issaris >Release: 3.2 >Organization: KUL >Environment: System: Linux takis 2.4.18 #17 Wed Aug 14 10:39:43 CEST 2002 i686 unknown Architecture: i686 Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz stepping 4 Debian GNU/Linux Woody 3.0 Linux takis 2.4.18 #17 Wed Aug 14 10:39:43 CEST 2002 i686 unknown gcc (GCC) 3.2 GNU objdump 2.12.90.0.1 20020307 Debian/GNU Linux host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: /home/takis/asm/gcc-3.2/configure --prefix=/usr/local/gcc-3.2 >Description: When compiling GCC 3.2 with GCC-3.2 on a x86 host for a PowerPC target, GCC 3.2 crashes. The following commandline was used: ../gcc-3.2/configure --target=powerpc-eabi --prefix=/usr/local/gcc-3.2-ppc --without-headers --with-newlib 2>&1 | tee configure.log make all-gcc install-gcc 2>&1 | tee make.log Please note that gccbug automatically included info about the choosen target in the "Environment" section, which is incorrect. It shows an incorrect configure commandline and an incorrect target. >How-To-Repeat: Command triggering the GCC crash: /home/takis/asm/gcc-build-ppc/gcc/xgcc -B/home/takis/asm/gcc-build-ppc/gcc/ -nostdinc -B/home/takis/asm/gcc-build-ppc/powerpc-eabi/newlib/ -isystem /home/takis/asm/gcc-build-ppc/powerpc-eabi/newlib/targ-include -isystem /home/takis/asm/gcc-3.2/newlib/libc/include -B/usr/local/gcc-3.2-ppc/powerpc-eabi/bin/ -B/usr/local/gcc-3.2-ppc/powerpc-eabi/lib/ -isystem /usr/local/gcc-3.2-ppc/powerpc-eabi/include -S tmp-dum.c -save-temps Contents of tmp-dum.c: int xxy_us_dummy; Contents of tmp-dum.i: # 1 "tmp-dum.c" # 1 "<built-in>" # 1 "<command line>" # 1 "tmp-dum.c" int xxy_us_dummy; >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-08-19 15:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1029772142.24540.155.camel@takis \ --to=panagiotis.issaris@mech.kuleuven.ac.be \ --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).