public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bryan@ixiacom.com To: gcc-gnats@gcc.gnu.org Cc: yossi@ixiacom.com Subject: target/3418: --with-cpu=403 flag results in broken xgcc which segfaults on tmp-dum.c Date: Mon, 25 Jun 2001 16:46:00 -0000 [thread overview] Message-ID: <20010625234323.914.qmail@sourceware.cygnus.com> (raw) >Number: 3418 >Category: target >Synopsis: --with-cpu=403 flag results in broken xgcc which segfaults on tmp-dum.c >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jun 25 16:46:02 PDT 2001 >Closed-Date: >Last-Modified: >Originator: bryan@ixiacom.com >Release: gcc-3.0 >Organization: >Environment: Linux squirt 2.4.5 #1 SMP Tue Jun 19 14:40:05 PDT 2001 i686 unknown running Debian unstable sid (identical problem on a Debian stable machine running Linux 2.2.19) >Description: configuring as described results in a broken xgcc cross compiler which segfaults during the all-gcc build process. every C file tried results in a segfault, even ones as simple as tmp-dum.c ("int xxy_us_dummy;") omitting the"--with-cpu=403" flag results in a successful build and a working compiler, but one which is not for the 40X family of PowerPC CPUs. >How-To-Repeat: configure as follows: ../gcc-3.0/configure --target=powerpc-linux --enable-languages=c --without-fp --with-cpu=403 run "make all-gcc" >Fix: unknown. if the "--with-cpu=403" flag is omitted, the resulting compiler is not for the embedded 405CR/405GP architecture. specifically, there are problems running the resulting code if it uses long long or structure assignment. (both of which work using an older gcc-3_0-branch snapshot that built OK with the "--with-cpu=403" flag) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-06-25 16:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-25 16:46 bryan [this message] 2002-04-05 2:35 rth
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=20010625234323.914.qmail@sourceware.cygnus.com \ --to=bryan@ixiacom.com \ --cc=gcc-gnats@gcc.gnu.org \ --cc=yossi@ixiacom.com \ /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).