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 ipa/105306] New: [12 Regression] ICE: verify_cgraph_node failed (error: semantic interposition mismatch)
Date: Tue, 19 Apr 2022 06:27:50 +0000 [thread overview]
Message-ID: <bug-105306-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105306
Bug ID: 105306
Summary: [12 Regression] ICE: verify_cgraph_node failed (error:
semantic interposition mismatch)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
g++ 12.0.1 20220417 snapshot (g:000c1b89d259fadb466e1f2e63c79da45fd17372) ICEs
when compiling gcc/testsuite/g++.dg/opt/pr59947.C w/ -Ofast:
% g++-12.0.1 -Ofast -c gcc/testsuite/g++.dg/opt/pr59947.C
gcc/testsuite/g++.dg/opt/pr59947.C:34:24: error: semantic interposition
mismatch
34 | template class E <char>;
| ^
_ZN1BD1Ev/6 (B::~B()) @0x7fdd9c891880
Type: function definition analyzed alias cpp_implicit_alias
Visibility: externally_visible public weak comdat comdat_group:_ZN1BD5Ev
one_only
Same comdat group as: _ZN1BD2Ev/5
References: _ZN1BD2Ev/5 (alias)
Referring:
Availability: available
Function flags:
Called by: _ZN1CI1DED2Ev/9
Calls:
during IPA pass: visibility
gcc/testsuite/g++.dg/opt/pr59947.C:34:24: internal compiler error:
verify_cgraph_node failed
0xcfe1e0 cgraph_node::verify_node()
/var/tmp/portage/sys-devel/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/cgraph.cc:3873
0xced4f4 symtab_node::verify()
/var/tmp/portage/sys-devel/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/symtab.cc:1359
0xcee6e7 symtab_node::verify_symtab_nodes()
/var/tmp/portage/sys-devel/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/symtab.cc:1387
0xfb169c symtab_node::checking_verify_symtab_nodes()
/var/tmp/portage/sys-devel/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/cgraph.h:682
0xfb169c symbol_table::remove_unreachable_nodes(_IO_FILE*)
/var/tmp/portage/sys-devel/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/ipa.cc:679
0x10c9be9 execute_todo
/var/tmp/portage/sys-devel/gcc-12.0.1_p20220417/work/gcc-12-20220417/gcc/passes.cc:2153
next reply other threads:[~2022-04-19 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 6:27 asolokha at gmx dot com [this message]
2022-04-19 9:35 ` [Bug ipa/105306] " rguenth at gcc dot gnu.org
2022-04-19 9:57 ` jakub at gcc dot gnu.org
2022-04-19 10:01 ` jakub at gcc dot gnu.org
2022-04-19 10:08 ` marxin at gcc dot gnu.org
2022-04-19 11:58 ` jakub at gcc dot gnu.org
2022-04-20 7:25 ` cvs-commit at gcc dot gnu.org
2022-04-20 7:25 ` 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-105306-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).