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/110620] spurious array-bounds
Date: Tue, 11 Jul 2023 08:01:19 +0000	[thread overview]
Message-ID: <bug-110620-4-H8gIM6kDfX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110620-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-07-11
     Ever confirmed|0                           |1

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  We diagnose

  _41 = operator new (8);

  <bb 3> [local count: 1014634345]:
  # iftmp.3_28 = PHI <_41(2)>
...
  <bb 9> [local count: 507317173]: 
  MEM[(struct value_type &)iftmp.3_28 + 24].first = 0;

and this access _is_ out of bounds, it's just in an unreachable path we
have not yet proved to be unreachable.

      parent reply	other threads:[~2023-07-11  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 19:16 [Bug c++/110620] New: " cuzdav at gmail dot com
2023-07-10 19:24 ` [Bug tree-optimization/110620] " cuzdav at gmail dot com
2023-07-10 19:27 ` cuzdav at gmail dot com
2023-07-10 19:28 ` cuzdav at gmail dot com
2023-07-10 19:30 ` cuzdav at gmail dot com
2023-07-10 19:39 ` pinskia at gcc dot gnu.org
2023-07-11  8:01 ` 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-110620-4-H8gIM6kDfX@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).