public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106943] GCC building clang/llvm with LTO flags causes ICE in clang
Date: Fri, 12 May 2023 19:10:26 +0000 [thread overview]
Message-ID: <bug-106943-4-T0Ou0E73XT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106943-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106943
--- Comment #24 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Appreciate the advice. So far I've managed to reduce the number of LTO inputs
down to two files, RegisterBankInfo.cpp.o plus APInt.cpp.o. I also built
gcc-12.3 with lineinfo and have a better backtrace:
during GIMPLE pass: thread
/tmp/llvm-project-llvmorg-13.0.1/llvm/lib/CodeGen/GlobalISel/RegisterBankInfo.cpp:
In member function 'verify':
/tmp/llvm-project-llvmorg-13.0.1/llvm/lib/CodeGen/GlobalISel/RegisterBankInfo.cpp:548:6:
internal compiler error: Segmentation fault
548 | bool RegisterBankInfo::ValueMapping::verify(unsigned
MeaningfulBitWidth) const {
| ^
0xb369ef crash_signal
../../gcc-12.3.0/gcc/toplev.cc:322
0x17f8977 operator_bitwise_not::fold_range(irange&, tree_node*, irange const&,
irange const&, tree_code) const
../../gcc-12.3.0/gcc/range-op.cc:3479
0x17f8977 operator_bitwise_not::fold_range(irange&, tree_node*, irange const&,
irange const&, tree_code) const
../../gcc-12.3.0/gcc/range-op.cc:3465
0x171cd0a fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:608
0x171e7e0 fold_using_range::fold_stmt(irange&, gimple*, fur_source&,
tree_node*)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:554
0x171eb4c fold_range(irange&, gimple*, range_query*)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:315
0xc985fd path_range_query::range_of_stmt(irange&, gimple*, tree_node*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:771
0xc99bc4 path_range_query::range_defined_in_block(irange&, tree_node*,
basic_block_def*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:356
0xc99dde path_range_query::internal_range_of_expr(irange&, tree_node*, gimple*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:209
0xc99dde path_range_query::internal_range_of_expr(irange&, tree_node*, gimple*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:193
0xc99ef0 path_range_query::range_of_expr(irange&, tree_node*, gimple*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:225
0x171cabf fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:602
0x171e7e0 fold_using_range::fold_stmt(irange&, gimple*, fur_source&,
tree_node*)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:554
0x171eb4c fold_range(irange&, gimple*, range_query*)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:315
0xc985fd path_range_query::range_of_stmt(irange&, gimple*, tree_node*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:771
0xc99bc4 path_range_query::range_defined_in_block(irange&, tree_node*,
basic_block_def*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:356
0xc99dde path_range_query::internal_range_of_expr(irange&, tree_node*, gimple*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:209
0xc99dde path_range_query::internal_range_of_expr(irange&, tree_node*, gimple*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:193
0xc99ef0 path_range_query::range_of_expr(irange&, tree_node*, gimple*)
../../gcc-12.3.0/gcc/gimple-range-path.cc:225
0x171ccab fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
../../gcc-12.3.0/gcc/gimple-range-fold.cc:602
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
next prev parent reply other threads:[~2023-05-12 19:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:39 [Bug c++/106943] New: " immoloism at googlemail dot com
2022-09-14 17:39 ` [Bug c++/106943] " immoloism at googlemail dot com
2022-09-14 17:50 ` pinskia at gcc dot gnu.org
2022-09-14 19:49 ` immoloism at googlemail dot com
2022-09-15 7:17 ` rguenth at gcc dot gnu.org
2022-09-19 14:12 ` immoloism at googlemail dot com
2023-05-11 12:49 ` amonakov at gcc dot gnu.org
2023-05-11 19:39 ` amonakov at gcc dot gnu.org
2023-05-11 20:29 ` amonakov at gcc dot gnu.org
2023-05-12 13:14 ` xry111 at gcc dot gnu.org
2023-05-12 13:27 ` amonakov at gcc dot gnu.org
2023-05-12 13:32 ` xry111 at gcc dot gnu.org
2023-05-12 14:00 ` amonakov at gcc dot gnu.org
2023-05-12 14:09 ` hubicka at gcc dot gnu.org
2023-05-12 14:23 ` amonakov at gcc dot gnu.org
2023-05-12 14:29 ` Jan Hubicka
2023-05-12 14:29 ` hubicka at ucw dot cz
2023-05-12 14:41 ` xry111 at gcc dot gnu.org
2023-05-12 14:57 ` amonakov at gcc dot gnu.org
2023-05-12 15:16 ` xry111 at gcc dot gnu.org
2023-05-12 15:29 ` hubicka at ucw dot cz
2023-05-12 15:45 ` xry111 at gcc dot gnu.org
2023-05-12 15:48 ` amonakov at gcc dot gnu.org
2023-05-12 15:55 ` amonakov at gcc dot gnu.org
2023-05-12 16:56 ` pinskia at gcc dot gnu.org
2023-05-12 19:10 ` amonakov at gcc dot gnu.org [this message]
2023-05-12 19:19 ` pinskia at gcc dot gnu.org
2023-05-12 19:27 ` amonakov at gcc dot gnu.org
2023-05-12 19:30 ` pinskia at gcc dot gnu.org
2023-05-13 3:18 ` xry111 at gcc dot gnu.org
2023-05-13 3:19 ` xry111 at gcc dot gnu.org
2023-05-13 5:29 ` xry111 at gcc dot gnu.org
2023-05-13 6:30 ` amonakov at gcc dot gnu.org
2023-05-13 7:58 ` amonakov at gcc dot gnu.org
2023-05-13 20:06 ` xry111 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-106943-4-T0Ou0E73XT@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).