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/47228] [4.6 Regression] wrong code with loop Date: Wed, 26 Jan 2011 09:53:00 -0000 [thread overview] Message-ID: <bug-47228-4-3d6PUJcsos@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47228-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47228 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 CC| |jamborm at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-01-26 08:28:31 UTC --- Yeah, clearly SRA fault, as it replaces b[x_1] = c; where both lhs and rhs is correctly type S, i.e. 3 byte packed BLKmode structure, with MEM_REF store which is SImode 4 byte.
next prev parent reply other threads:[~2011-01-26 8:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-25 23:05 [Bug c/47228] New: likely improper segfault in generated code LpSolit at netscape dot net 2011-01-26 0:17 ` [Bug tree-optimization/47228] [4.6 Regression] wrong code with loop pinskia at gcc dot gnu.org 2011-01-26 9:50 ` jakub at gcc dot gnu.org 2011-01-26 9:50 ` jakub at gcc dot gnu.org 2011-01-26 9:53 ` jakub at gcc dot gnu.org [this message] 2011-01-26 19:58 ` jamborm at gcc dot gnu.org 2011-01-26 21:14 ` jamborm at gcc dot gnu.org 2011-01-27 14:10 ` jamborm at gcc dot gnu.org 2011-01-27 14:26 ` jamborm at gcc dot gnu.org 2011-02-02 18:16 ` dnovillo 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-47228-4-3d6PUJcsos@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).