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/58404] New: &noninvariant_address not forwproped into ->handled_component Date: Thu, 12 Sep 2013 10:42:00 -0000 [thread overview] Message-ID: <bug-58404-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58404 Bug ID: 58404 Summary: &noninvariant_address not forwproped into ->handled_component Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org On: struct S { int s; }; S a[1024]; void foo () { for (int i = 0; i < 1024; i++) { S &r = a[i]; r.s++; } } we don't forwprop r_4 = &a[i_9]; r_4->s = 2; even when a[i_9].s is valid is_gimple_val. Seen on libgomp.c++/simd-6.C on gomp-4_0-branch.
next reply other threads:[~2013-09-12 10:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-12 10:42 jakub at gcc dot gnu.org [this message] 2013-09-12 10:43 ` [Bug tree-optimization/58404] " rguenth at gcc dot gnu.org 2013-09-12 13:20 ` rguenth at gcc dot gnu.org 2013-09-12 13:20 ` rguenth 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-58404-4@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).