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/110896] [12/13/14 Regression] gcc.dg/ubsan/pr81981.c is xfailed
Date: Fri, 04 Aug 2023 07:07:13 +0000	[thread overview]
Message-ID: <bug-110896-4-ilBLrtgLFS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110896-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110896

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-08-04

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
We simplify this to t[0] * 2 (by luck, so it could also be u[0] * 2) which
means we lose track of the use of the other variable.

Value numbering stmt = t$0_4 = PHI <t$0_13(D)(2), t$0_15(3)>
Setting value number of t$0_4 to t$0_4 (changed)
Making available beyond BB4 t$0_4 for value t$0_4
Value numbering stmt = u$0_12 = PHI <u$0_14(D)(2), u$0_16(3)>
Marking CSEd to PHI node t$0_4 = PHI <t$0_13(D)(2), t$0_15(3)>
Setting value number of u$0_12 to t$0_4 (changed)
...
Replaced redundant PHI node defining u$0_12 with t$0_4
gimple_simplified to _9 = t$0_4 * 2;

early uninit sees conditional init of the memory and so refrains from
diagnosing this.

I suppose this is kind-of a duplicate of the many missed uninit diagnostics
because of CCP optimistic propagation (and only because we don't do optimistic
copyprop we do not have even more such cases).

  parent reply	other threads:[~2023-08-04  7:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 22:46 [Bug tree-optimization/110896] New: " pinskia at gcc dot gnu.org
2023-08-03 22:47 ` [Bug tree-optimization/110896] " pinskia at gcc dot gnu.org
2023-08-04  7:07 ` rguenth at gcc dot gnu.org [this message]
2024-03-07 23:26 ` law 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-110896-4-ilBLrtgLFS@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: link
Be 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).