public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/50448] [4.3/4.5/4.6/4.7 Regression] Missed optimization accessing struct component with integer address Date: Thu, 29 Sep 2011 16:00:00 -0000 [thread overview] Message-ID: <bug-50448-4-h1IjJ0Cfft@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50448-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50448 Georg-Johann Lay <gjl at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |middle-end Known to work| |3.4.6 Summary|[avr] Missed optimization |[4.3/4.5/4.6/4.7 |accessing struct component |Regression] Missed |with integer address |optimization accessing | |struct component with | |integer address Known to fail| |4.7.0 --- Comment #1 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-09-29 15:55:05 UTC --- As explained in http://gcc.gnu.org/ml/gcc/2011-09/msg00353.html this looks like a middle-end flaw during tree -> RTL lowering in explow.c:memory_address_addr_space() where the target cannot do anything about. Changed component from TARGET to MIDDLE-END.
next prev parent reply other threads:[~2011-09-29 15:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-18 13:38 [Bug target/50448] New: [avr] Missed optimization accessing struct component with known, absolute address gjl at gcc dot gnu.org 2011-09-18 13:41 ` [Bug target/50448] " gjl at gcc dot gnu.org 2011-09-29 16:00 ` gjl at gcc dot gnu.org [this message] 2011-10-27 10:25 ` [Bug middle-end/50448] [4.5/4.6/4.7 Regression] Missed optimization accessing struct component with integer address rguenth at gcc dot gnu.org 2011-10-28 13:00 ` gjl at gcc dot gnu.org 2011-10-28 14:27 ` bonzini at gnu dot org 2011-11-03 11:02 ` [Bug rtl-optimization/50448] " gjl at gcc dot gnu.org 2011-11-05 13:09 ` gjl at gcc dot gnu.org 2011-11-05 20:37 ` gjl 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-50448-4-h1IjJ0Cfft@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).