public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106206] New: [12/13 Regression] ICE: canonical types differ for identical types 'int(...)' and 'int(...)'
Date: Tue, 05 Jul 2022 18:46:11 +0000 [thread overview]
Message-ID: <bug-106206-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106206
Bug ID: 106206
Summary: [12/13 Regression] ICE: canonical types differ for
identical types 'int(...)' and 'int(...)'
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started between 20210627 and 20210704, with file g++.dg/abi/covariant3.C :
(gcc configured with --enable-checking=yes)
$ gcc-11 -c covariant3.C -O2 -fprofile-arcs -fanalyzer
$
$ gcc-13-20220703 -c covariant3.C -O2 -fprofile-arcs -fanalyzer
during IPA pass: analyzer
cc1plus: internal compiler error: canonical types differ for identical types
'int(...)' and 'int(...)'
0xa4d28c comptypes(tree_node*, tree_node*, int)
../../gcc/cp/typeck.cc:1560
0xa4c0a4 structural_comptypes
../../gcc/cp/typeck.cc:1463
0xa4d240 comptypes(tree_node*, tree_node*, int)
../../gcc/cp/typeck.cc:1553
0xa4c0a4 structural_comptypes
../../gcc/cp/typeck.cc:1463
0xa4d240 comptypes(tree_node*, tree_node*, int)
../../gcc/cp/typeck.cc:1553
0x7c8fe8 cxx_types_compatible_p(tree_node*, tree_node*)
../../gcc/cp/cp-objcp-common.cc:126
0xaf3842 c_fold_indirect_ref_for_warn
../../gcc/c-family/c-pretty-print.cc:1834
0xaf3b65 c_fold_indirect_ref_for_warn
../../gcc/c-family/c-pretty-print.cc:1902
0xaf3b65 c_fold_indirect_ref_for_warn
../../gcc/c-family/c-pretty-print.cc:1902
0xaf4e8c print_mem_ref
../../gcc/c-family/c-pretty-print.cc:1964
0x8491cc expr_to_string(tree_node*)
../../gcc/cp/error.cc:3289
0x849b8c cp_printer
../../gcc/cp/error.cc:4458
0x2179080 pp_format(pretty_printer*, text_info*)
../../gcc/pretty-print.cc:1475
0x151db3a ana::evdesc::event_desc::formatted_print(char const*, ...) const
../../gcc/analyzer/pending-diagnostic.cc:114
0x20e3b96 ana::warning_event::get_desc(bool) const
../../gcc/analyzer/checker-path.cc:1136
0x20e35a2 ana::checker_event::prepare_for_emission(ana::checker_path*,
ana::pending_diagnostic*, diagnostic_event_id_t)
../../gcc/analyzer/checker-path.cc:237
0x2103d48 ana::checker_path::prepare_for_emission(ana::pending_diagnostic*)
../../gcc/analyzer/checker-path.h:652
0x2103d48 ana::diagnostic_manager::emit_saved_diagnostic(ana::exploded_graph
const&, ana::saved_diagnostic const&)
../../gcc/analyzer/diagnostic-manager.cc:1396
0x2104861 ana::dedupe_winners::emit_best(ana::diagnostic_manager*,
ana::exploded_graph const&)
../../gcc/analyzer/diagnostic-manager.cc:1296
0x2104861 ana::diagnostic_manager::emit_saved_diagnostics(ana::exploded_graph
const&)
../../gcc/analyzer/diagnostic-manager.cc:1348
next reply other threads:[~2022-07-05 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 18:46 gscfq@t-online.de [this message]
2022-07-05 19:05 ` [Bug analyzer/106206] " mpolacek at gcc dot gnu.org
2023-05-08 12:24 ` [Bug analyzer/106206] [12/13/14 Regression] ICE: canonical types differ for identical types 'int(...)' and 'int(...)' since r12-1931-ge61ffa201403e3 rguenth 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-106206-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).