public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107353] [13 regression] Numerous ICEs after r13-3416-g1d561e1851c466
Date: Tue, 25 Oct 2022 07:49:13 +0000 [thread overview]
Message-ID: <bug-107353-4-WMpcPPEcEk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107353-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107353
--- Comment #10 from Arseny Solokha <asolokha at gmx dot com> ---
g++ 13.0.0 20221023 snapshot (g:0e37fd4dc74c1db99cdc7d71ef378e1221253c6f) ICEs
when compiling the following testcase, reduced from
test/CodeGenCXX/cxx11-thread-local.cpp from the clang 14 test suite:
struct Dtor;
template <typename> struct X { static thread_local Dtor m; };
template <typename T> thread_local Dtor X<T>::m;
extern template Dtor X<char>::m;
void *e2 = &X<char>::m;
% x86_64-pc-linux-gnu-g++-13 -c uuir2io5.cpp
during IPA pass: whole-program
uuir2io5.cpp:5:23: internal compiler error: in
function_and_variable_visibility, at ipa-visibility.cc:889
5 | void *e2 = &X<char>::m;
| ^
0x9403cc function_and_variable_visibility
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/ipa-visibility.cc:889
0x20fe8a6 whole_program_function_and_variable_visibility
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/ipa-visibility.cc:940
0x20fe8a6 execute
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/ipa-visibility.cc:988
next prev parent reply other threads:[~2022-10-25 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 22:53 [Bug other/107353] New: [13 regression] Numerous ICEs after 13-3416-g1d561e1851c466 seurer at gcc dot gnu.org
2022-10-21 22:56 ` [Bug other/107353] " seurer at gcc dot gnu.org
2022-10-21 23:30 ` law at gcc dot gnu.org
2022-10-22 8:49 ` [Bug other/107353] [13 regression] Numerous ICEs after r13-3416-g1d561e1851c466 iains at gcc dot gnu.org
2022-10-22 11:17 ` iains at gcc dot gnu.org
2022-10-24 13:00 ` rguenth at gcc dot gnu.org
2022-10-24 20:42 ` segher at gcc dot gnu.org
2022-10-25 6:43 ` amonakov at gcc dot gnu.org
2022-10-25 6:54 ` asolokha at gmx dot com
2022-10-25 7:00 ` amonakov at gcc dot gnu.org
2022-10-25 7:11 ` amonakov at gcc dot gnu.org
2022-10-25 7:49 ` asolokha at gmx dot com [this message]
2022-10-25 14:11 ` amonakov at gcc dot gnu.org
2022-10-25 16:08 ` amonakov at gcc dot gnu.org
2022-10-25 17:51 ` amonakov at gcc dot gnu.org
2022-10-26 16:30 ` cvs-commit at gcc dot gnu.org
2022-10-26 17:02 ` [Bug other/107353] frontends sometimes select wrong (too strong) TLS access model amonakov at gcc dot gnu.org
2023-04-26 6:56 ` rguenth at gcc dot gnu.org
2023-07-27 9:24 ` rguenth at gcc dot gnu.org
2024-05-21 9:12 ` 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-107353-4-WMpcPPEcEk@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).