public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/113198] New: [14 Regression] internal compiler error: 'verify_type' failed
Date: Tue, 02 Jan 2024 11:23:59 +0000 [thread overview]
Message-ID: <bug-113198-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113198
Bug ID: 113198
Summary: [14 Regression] internal compiler error: 'verify_type'
failed
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
seen with trunk 20240101 on at least x86_64-linux-gnu and
powerpc64le-linux-gnu, building the actiona package. The internal retrying
fails, however this is 100% reproducible.
https://launchpadlibrarian.net/706902792/buildlog_ubuntu-noble-amd64.actiona_3.10.1-1build3_BUILDING.txt.gz
usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1567:12: error: type
variant has different 'TYPE_FIELDS'
1567 | struct IsQEnumHelper {
| ^~~~~~~~~~~~~
[...]
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:1567:12: internal compiler
error: 'veri
fy_type' failed
0x704dab verify_type(tree_node const*)
../../src/gcc/tree.cc:14386
0x1cedf12 gen_type_die_with_usage
../../src/gcc/dwarf2out.cc:26226
0x1cee155 gen_type_die_with_usage
../../src/gcc/dwarf2out.cc:26359
0x1cedc3a gen_type_die
../../src/gcc/dwarf2out.cc:26457
0x1cd9c1e gen_decl_die
../../src/gcc/dwarf2out.cc:27058
0x1cf14f0 gen_member_die
../../src/gcc/dwarf2out.cc:25910
0x1cf14f0 gen_struct_or_union_type_die
../../src/gcc/dwarf2out.cc:26006
0x1cf14f0 gen_tagged_type_die
../../src/gcc/dwarf2out.cc:26207
0x1cee11d gen_type_die_with_usage
../../src/gcc/dwarf2out.cc:26401
0x1cedc3a gen_type_die
../../src/gcc/dwarf2out.cc:26457
0x1cd9af2 gen_decl_die
../../src/gcc/dwarf2out.cc:27097
0x1ca7055 dwarf2out_decl
../../src/gcc/dwarf2out.cc:27655
0x1ce3fdc dwarf2out_type_decl
../../src/gcc/dwarf2out.cc:27373
0x1ce3fdc rest_of_type_compilation(tree_node*, int)
../../src/gcc/passes.cc:339
0x1e13490 finish_struct_1(tree_node*)
../../src/gcc/cp/class.cc:7725
0x2005358 instantiate_class_template(tree_node*)
../../src/gcc/cp/pt.cc:12637
0x1cada38 complete_type(tree_node*)
../../src/gcc/cp/typeck.cc:138
0x1db5111 lookup_member(tree_node*, tree_node*, int, bool, int,
access_failure_info*)
../../src/gcc/cp/search.cc:1198
0x1d6fc3f lookup_qualified_name(tree_node*, tree_node*, LOOK_want, bool)
../../src/gcc/cp/name-lookup.cc:7192
0x2043402 tsubst_qualified_id
../../src/gcc/cp/pt.cc:17173
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-14/README.Bugs> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[3]: *** [Makefile:2453: generated/codelineedit.o] Error 1
next reply other threads:[~2024-01-02 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 11:23 doko at gcc dot gnu.org [this message]
2024-01-02 22:15 ` [Bug middle-end/113198] " pinskia 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-113198-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).