public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/51117] [4.7 regression] rev.181172 causes glibc build failure Date: Mon, 05 Dec 2011 14:57:00 -0000 [thread overview] Message-ID: <bug-51117-4-g64h4Gj0db@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51117-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51117 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-05 14:57:39 UTC --- I agree it is a gcc bug, please see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51275 for more information.
next prev parent reply other threads:[~2011-12-05 14:57 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-13 12:42 [Bug tree-optimization/51117] New: " markus at trippelsdorf dot de 2011-11-15 10:50 ` [Bug tree-optimization/51117] " izamyatin at gmail dot com 2011-11-15 16:27 ` matz at gcc dot gnu.org 2011-11-29 19:03 ` rth at gcc dot gnu.org 2011-12-05 14:11 ` rguenth at gcc dot gnu.org 2011-12-05 14:57 ` jakub at gcc dot gnu.org [this message] 2011-12-06 1:06 ` jsm28 at gcc dot gnu.org 2011-12-08 17:40 ` jakub at gcc dot gnu.org 2011-12-09 11:54 ` jakub at gcc dot gnu.org 2011-12-09 16:18 ` jakub at gcc dot gnu.org 2011-12-09 20:52 ` jakub at gcc dot gnu.org 2011-12-13 14:01 ` matz at gcc dot gnu.org 2011-12-13 14:08 ` jakub at gcc dot gnu.org 2011-12-15 17:31 ` jakub 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-51117-4-g64h4Gj0db@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).