public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108253] New: [13 Regression] ICE in set_nonzero_bits
Date: Thu, 29 Dec 2022 18:37:21 +0000 [thread overview]
Message-ID: <bug-108253-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108253
Bug ID: 108253
Summary: [13 Regression] ICE in set_nonzero_bits
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
Target: x86_64
Created attachment 54167
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54167&action=edit
Testcase
I'm assuming this is a regression as I suspect the abseil-cpp package was
around and built during the f36/f37 gcc-12 cycle.
g++ -O2
./absl/strings/CMakeFiles/absl_cord_ring_reader_test.dir/cord_ring_reader_test.cc.ii
during GIMPLE pass: dom
/builddir/build/BUILD/abseil-cpp-20220623.1/absl/strings/cord_ring_reader_test.cc:
In member function 'virtual void
absl::lts_20220623::cord_internal::{anonymous}::CordRingReaderTest_DefaultInstance_Test::TestBody()':
/builddir/build/BUILD/abseil-cpp-20220623.1/absl/strings/cord_ring_reader_test.cc:58:1:
internal compiler error: in set_nonzero_bits, at tree-ssanames.cc:464
58 | TEST(CordRingReaderTest, DefaultInstance) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libbacktrace could not find executable to open
Please submit a full bug report, with preprocessed source.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
I haven't reduced or debugged this at all. It could well land on me as it's
failing in DOM. It could also well land on Aldy/Andrew since I suspect it's
touching ranger from inside DOM.
next reply other threads:[~2022-12-29 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 18:37 law at gcc dot gnu.org [this message]
2022-12-29 18:48 ` [Bug tree-optimization/108253] " pinskia at gcc dot gnu.org
2022-12-29 18:53 ` pinskia at gcc dot gnu.org
2022-12-30 6:41 ` pinskia at gcc dot gnu.org
2022-12-30 6:48 ` pinskia at gcc dot gnu.org
2022-12-30 7:04 ` pinskia at gcc dot gnu.org
2023-01-03 15:09 ` jakub at gcc dot gnu.org
2023-01-04 11:17 ` cvs-commit at gcc dot gnu.org
2023-01-04 11:17 ` jakub 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-108253-4@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).