public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113693] ICE: in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:647 with _BitInt() at -O2 -fdbg-cnt=vect_loop:1
Date: Thu, 01 Feb 2024 10:13:07 +0000 [thread overview]
Message-ID: <bug-113693-4-UKb1NiowSG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113693-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113693
--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:b84f8a5e0a7ef3e5bd0d186fc7e280d9c43c5b7f
commit r14-8683-gb84f8a5e0a7ef3e5bd0d186fc7e280d9c43c5b7f
Author: Richard Biener <rguenther@suse.de>
Date: Thu Feb 1 09:18:47 2024 +0100
tree-optimization/113693 - LC SSA and region VN
The following fixes LC SSA preserving with region VN which was broken
when availability checking was enhanced to treat not visited value
numbers as available. The following makes sure to honor availability
data we put in place for LC SSA preserving instead.
PR tree-optimization/113693
* tree-ssa-sccvn.cc (rpo_elim::eliminate_avail): Honor avail
data when available.
* gcc.dg/pr113693.c: New testcase.
next prev parent reply other threads:[~2024-02-01 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 21:35 [Bug tree-optimization/113693] New: " zsojka at seznam dot cz
2024-01-31 22:34 ` [Bug tree-optimization/113693] " pinskia at gcc dot gnu.org
2024-02-01 8:09 ` rguenth at gcc dot gnu.org
2024-02-01 10:13 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-01 10:23 ` 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-113693-4-UKb1NiowSG@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).