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/101641] Bogus redundant store removal Date: Thu, 29 Jul 2021 08:55:57 +0000 [thread overview] Message-ID: <bug-101641-4-f4nOR23ilD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101641-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101641 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- With union punning we've basically opened up a way to change the dynamic type of storage in a way that expects us from generating no code from a "virtual" read-write cycle involving the previous and the next dynamic type of the storage. Now the checks we're currently performing try to assess whether such a change takes place but given we don't really know the current dynamic type we're guessing based on the "read" which constrains that dynamic type. And we're willing to elide changes to a type that is strictly more restrictive as to what followon accesses it allows. What goes wrong here is our guessing of the current dynamic type based on the observed read, that's because the read picks up *py but the reads alias-set is not equal to or a subset of the *py stores alias-set (but it conflicts since the subset relation is the other way around). What we know from the union read is that the dynamic type is either the union type (so the read can pun) or the dynamic type is the union member type (then the read cannot pun). 6.5/7 allows accesses using "an aggregate or union type that includes [a type compatible with the effective type of the object]". Though the 'aggregate' case appears quite odd to me, does it really allow 'int i; struct { float f; int i; } *p = &i; float x = p->f;'? GCC doesn't allow this already based on the fact that sizeof (*p) is larger than 'i', thus would even disallow it in case the 'f' member was 'int' as well.
next prev parent reply other threads:[~2021-07-29 8:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-27 12:03 [Bug tree-optimization/101641] New: " rguenth at gcc dot gnu.org 2021-07-27 12:08 ` [Bug tree-optimization/101641] " rguenth at gcc dot gnu.org 2021-07-29 8:09 ` rguenth at gcc dot gnu.org 2021-07-29 8:55 ` rguenth at gcc dot gnu.org [this message] 2021-07-29 9:07 ` rguenth at gcc dot gnu.org 2021-07-29 18:04 ` muecker at gwdg dot de 2021-09-10 8:05 ` rguenth at gcc dot gnu.org 2021-09-28 10: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-101641-4-f4nOR23ilD@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).