public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "moonshine at kapsi dot fi" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/44865] Compiling a single file with -O3 -march=pentium4 -flto ICEs Date: Thu, 08 Jul 2010 03:46:00 -0000 [thread overview] Message-ID: <20100708034617.16276.qmail@sourceware.org> (raw) In-Reply-To: <bug-44865-19380@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from moonshine at kapsi dot fi 2010-07-08 03:46 ------- Created an attachment (id=21137) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21137&action=view) a preprocessed testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44865
next prev parent reply other threads:[~2010-07-08 3:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-08 3:45 [Bug lto/44865] New: " moonshine at kapsi dot fi 2010-07-08 3:46 ` moonshine at kapsi dot fi [this message] [not found] <bug-44865-4@http.gcc.gnu.org/bugzilla/> 2010-11-26 17:06 ` [Bug lto/44865] " rguenth at gcc dot gnu.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=20100708034617.16276.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).