public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kazu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/30669] New: i686-pc-linux-gnu doesn't build Date: Thu, 01 Feb 2007 15:05:00 -0000 [thread overview] Message-ID: <bug-30669-5009@http.gcc.gnu.org/bugzilla/> (raw) gcc segfaults while building libgcc, more specifically _multi3. Here is a reduced testcase: /* Compile this with ./cc1 -quiet -m64 -O2. */ typedef int TItype __attribute__ ((mode (TI))); void foo (TItype u __attribute__((unused))) { } -- Summary: i686-pc-linux-gnu doesn't build Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: kazu at gcc dot gnu dot org GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30669
next reply other threads:[~2007-02-01 15:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-01 15:05 kazu at gcc dot gnu dot org [this message] 2007-02-01 15:07 ` [Bug bootstrap/30669] " rguenth at gcc dot gnu dot org 2007-02-01 15:09 ` rguenth at gcc dot gnu dot org 2007-02-02 5:41 ` ian at airs dot com 2007-02-23 17:58 ` b33fc0d3 at gmail dot com 2007-02-23 20:21 ` ubizjak at gmail dot com
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=bug-30669-5009@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).