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/113898] [14 regression] ICE in copy_reference_ops_from_ref, at tree-ssa-sccvn.cc:1156 since r14-8929-g938a419182f
Date: Fri, 16 Feb 2024 08:29:42 +0000	[thread overview]
Message-ID: <bug-113898-4-kNAo53Xx32@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113898-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yes, that case is tracked in PR113895 - we value number

e[h_7(D)][1] = 4;

and out-of-bound array indices behave differently, choking the verifier code.
And I don't see an easy way to fix that so the plan is to remove the verifier
code (not sure if it's worth detecting those cases and selectively
disabling it).

Let's track this in the other bug.

      parent reply	other threads:[~2024-02-16  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  8:10 [Bug tree-optimization/113898] New: ICE in copy_reference_ops_from_ref, at tree-ssa-sccvn.cc:1156 shaohua.li at inf dot ethz.ch
2024-02-13  8:45 ` [Bug tree-optimization/113898] [14 regression] ICE in copy_reference_ops_from_ref, at tree-ssa-sccvn.cc:1156 since r14-8929-g938a419182f rguenth at gcc dot gnu.org
2024-02-13  9:01 ` rguenth at gcc dot gnu.org
2024-02-13 10:45 ` cvs-commit at gcc dot gnu.org
2024-02-13 10:49 ` rguenth at gcc dot gnu.org
2024-02-16  8:00 ` shaohua.li at inf dot ethz.ch
2024-02-16  8:29 ` 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-113898-4-kNAo53Xx32@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).