public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/30921] [4.3 Regression] Bootstrap failure with -ftree-vectorize on i386 Date: Thu, 22 Feb 2007 18:07:00 -0000 [thread overview] Message-ID: <20070222180710.32166.qmail@sourceware.org> (raw) In-Reply-To: <bug-30921-9531@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rth at gcc dot gnu dot org 2007-02-22 18:07 ------- I don't think this has anything to do with either vectorization or my patch. I was seeing that same failure with --with-arch=pentium4 before my patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30921
next prev parent reply other threads:[~2007-02-22 18:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-22 7:09 [Bug bootstrap/30921] New: " irar at il dot ibm dot com 2007-02-22 7:58 ` [Bug bootstrap/30921] " irar at il dot ibm dot com 2007-02-22 8:12 ` ubizjak at gmail dot com 2007-02-22 8:22 ` irar at il dot ibm dot com 2007-02-22 9:54 ` ubizjak at gmail dot com 2007-02-22 17:21 ` [Bug target/30921] [4.3 Regression] " pinskia at gcc dot gnu dot org 2007-02-22 18:07 ` rth at gcc dot gnu dot org [this message] 2007-02-23 0:43 ` pinskia at gcc dot gnu dot org
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=20070222180710.32166.qmail@sourceware.org \ --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).