public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/51759] [4.5 Regression] miscompile writes past end of bitfield Date: Mon, 09 Jan 2012 20:06:00 -0000 [thread overview] Message-ID: <bug-51759-4-AJfdPdiYPN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51759-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51759 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE --- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> 2012-01-09 20:05:27 UTC --- I have backported the fix to the 4.5 branch and also committed the testcase to the the 4.6 branch and trunk. Still it is a duplicate of PR 45644 and so I'm closing this as such. *** This bug has been marked as a duplicate of bug 45644 ***
prev parent reply other threads:[~2012-01-09 20:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-05 9:35 [Bug c++/51759] New: " nobled at dreamwidth dot org 2012-01-05 9:36 ` [Bug c++/51759] " nobled at dreamwidth dot org 2012-01-05 9:39 ` nobled at dreamwidth dot org 2012-01-05 10:00 ` [Bug tree-optimization/51759] [4.5 Regression] " rguenth at gcc dot gnu.org 2012-01-05 13:39 ` jamborm at gcc dot gnu.org 2012-01-06 13:33 ` jamborm at gcc dot gnu.org 2012-01-09 18:40 ` jamborm at gcc dot gnu.org 2012-01-09 19:52 ` jamborm at gcc dot gnu.org 2012-01-09 20:03 ` jamborm at gcc dot gnu.org 2012-01-09 20:06 ` jamborm at gcc dot gnu.org [this message]
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-51759-4-AJfdPdiYPN@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).