public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97464] Missed redundant store optimization opportunity Date: Mon, 19 Oct 2020 07:22:16 +0000 [thread overview] Message-ID: <bug-97464-4-rMwwW5SGiN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97464-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97464 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |rguenth at gcc dot gnu.org Component|c++ |tree-optimization Keywords| |alias, missed-optimization Last reconfirmed| |2020-10-19 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- In GCCs memory model x and y can still point to the same memory, the only thing that hints at this not being the case is the load from x at the --x; statement but we're eliminating this load (using TBAA) with the store from the ++x statement which means we get to see (at the store elimination phase) int tem = x; y = 1; x = tem; and here the store to x is necessary because x and y may now point to the same storage, each ending lifetime of the int/float object eventually live previously at the location. So yes, before eliminating dead code after eliminating redundancies we could have seen the store is not necessary (actually we still don't use the present load to do so). So, it's a difficult one. And I believe we have a duplicate report somewhere.
next prev parent reply other threads:[~2020-10-19 7:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-16 17:31 [Bug c++/97464] New: " pdimov at gmail dot com 2020-10-19 7:22 ` rguenth at gcc dot gnu.org [this message] 2021-08-15 0:18 ` [Bug tree-optimization/97464] " pinskia 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-97464-4-rMwwW5SGiN@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).