public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/50868] [4.7 Regression] 1x176.gcc in SPEC CPU 2000 failed to build with LTO Date: Tue, 25 Oct 2011 16:12:00 -0000 [thread overview] Message-ID: <bug-50868-4-hQWgiAs73L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50868-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50868 Markus Trippelsdorf <markus at trippelsdorf dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markus at trippelsdorf dot | |de --- Comment #1 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2011-10-25 16:12:12 UTC --- Dup of Bug 50823
next prev parent reply other threads:[~2011-10-25 16:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-25 15:48 [Bug middle-end/50868] New: " hjl.tools at gmail dot com 2011-10-25 16:12 ` markus at trippelsdorf dot de [this message] 2011-10-25 21:44 ` [Bug middle-end/50868] " rguenth at gcc dot gnu.org 2011-10-27 11:47 ` 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=bug-50868-4-hQWgiAs73L@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).