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/54498] [4.6 Regression] incorrect code generation from g++ -O Date: Fri, 12 Apr 2013 16:30:00 -0000 [thread overview] Message-ID: <bug-54498-4-TQZWJkcYMn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54498-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54498 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |jakub at gcc dot gnu.org Resolution| |FIXED Target Milestone|4.6.4 |4.7.2 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-12 16:30:08 UTC --- The 4.6 branch has been closed, fixed in GCC 4.7.2.
next prev parent reply other threads:[~2013-04-12 16:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-05 21:50 [Bug c++/54498] New: incorrect code generation from g++ -O on x86_64 stevenj at alum dot mit.edu 2012-09-05 22:22 ` [Bug tree-optimization/54498] [4.7/4.8 Regression] incorrect code generation from g++ -O pinskia at gcc dot gnu.org 2012-09-06 9:58 ` rguenth at gcc dot gnu.org 2012-09-06 10:21 ` rguenth at gcc dot gnu.org 2012-09-06 12:22 ` hjl.tools at gmail dot com 2012-09-06 13:54 ` [Bug tree-optimization/54498] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org 2012-09-06 14:48 ` rguenth at gcc dot gnu.org 2012-09-06 15:20 ` rguenth at gcc dot gnu.org 2012-09-07 8:20 ` [Bug tree-optimization/54498] [4.6 " rguenth at gcc dot gnu.org 2013-04-12 16:30 ` jakub at gcc dot gnu.org [this message] 2023-03-27 12:32 ` cvs-commit 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-54498-4-TQZWJkcYMn@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).