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 ipa/103875] Dead writes are not optimized out Date: Tue, 04 Jan 2022 14:09:03 +0000 [thread overview] Message-ID: <bug-103875-4-sg7Bo9KFje@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103875-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103875 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The clobber is gone at the point we inline pop(), CDDCE1 removes it because the clobbered address computation is dead. Eliminating unnecessary statements: Deleting : *_4 ={v} {CLOBBER}; Deleting : _4 = &this_6(D)->data[_2]; IL before CDDCE: <bb 2> : _1 = this_6(D)->size; _2 = _1 + 18446744073709551615; this_6(D)->size = _2; _4 = &this_6(D)->data[_2]; *_4 ={v} {CLOBBER}; return;
prev parent reply other threads:[~2022-01-04 14:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-31 13:08 [Bug pending/103875] New: " lh_mouse at 126 dot com 2021-12-31 14:14 ` [Bug ipa/103875] " pinskia at gcc dot gnu.org 2022-01-04 14:09 ` rguenth 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-103875-4-sg7Bo9KFje@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).