public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "shorne at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104153] [12 Regression] ICE due to recent ifcvt changes
Date: Tue, 08 Feb 2022 08:47:35 +0000 [thread overview]
Message-ID: <bug-104153-4-ckF9IqC9S2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104153-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104153
Stafford Horne <shorne at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shorne at gcc dot gnu.org
--- Comment #8 from Stafford Horne <shorne at gcc dot gnu.org> ---
I am seeing a similar ICE when building glibc.
/home/shorne/work/gnu-toolchain/gcc/libstdc++-v3/src/c++98/localename.cc: In
constructor 'std::locale::_Impl::_Impl(const char*, std::size_t)':
/home/shorne/work/gnu-toolchain/gcc/libstdc++-v3/src/c++98/localename.cc:315:3:
internal compiler error: in df_refs_verify, at df-scan.cc:4003
315 | }
| ^
0x6ad94e df_refs_verify
/home/shorne/work/gnu-toolchain/gcc/gcc/df-scan.cc:4003
0xc2d286 df_insn_refs_verify
/home/shorne/work/gnu-toolchain/gcc/gcc/df-scan.cc:4086
0xc2eefb df_bb_verify
/home/shorne/work/gnu-toolchain/gcc/gcc/df-scan.cc:4119
0xc2f28f df_scan_verify()
/home/shorne/work/gnu-toolchain/gcc/gcc/df-scan.cc:4240
0xc1bc14 df_verify()
/home/shorne/work/gnu-toolchain/gcc/gcc/df-core.cc:1818
0xc1bc14 df_analyze_1
/home/shorne/work/gnu-toolchain/gcc/gcc/df-core.cc:1214
0x177e1e1 execute_rtl_cprop
/home/shorne/work/gnu-toolchain/gcc/gcc/cprop.cc:1925
0x177e1e1 execute
/home/shorne/work/gnu-toolchain/gcc/gcc/cprop.cc:1964
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
I confirm the patch also fixes things for me.
next prev parent reply other threads:[~2022-02-08 8:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 0:12 [Bug rtl-optimization/104153] New: " law at gcc dot gnu.org
2022-01-21 0:14 ` [Bug rtl-optimization/104153] " pinskia at gcc dot gnu.org
2022-01-21 8:50 ` rguenth at gcc dot gnu.org
2022-01-21 10:56 ` rdapp at linux dot ibm.com
2022-01-21 18:23 ` law at gcc dot gnu.org
2022-01-21 21:03 ` rdapp at linux dot ibm.com
2022-01-24 8:51 ` pinskia at gcc dot gnu.org
2022-01-28 7:40 ` law at gcc dot gnu.org
2022-01-31 7:24 ` rdapp at linux dot ibm.com
2022-01-31 17:50 ` rdapp at linux dot ibm.com
2022-01-31 18:19 ` law at gcc dot gnu.org
2022-02-08 8:47 ` shorne at gcc dot gnu.org [this message]
2022-02-08 8:48 ` shorne at gcc dot gnu.org
2022-02-08 19:49 ` cvs-commit at gcc dot gnu.org
2022-02-13 18:29 ` 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-104153-4-ckF9IqC9S2@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).