public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105852] New: ice in instantiate_decl
Date: Sun, 05 Jun 2022 04:49:13 +0000 [thread overview]
Message-ID: <bug-105852-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105852
Bug ID: 105852
Summary: ice in instantiate_decl
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Created attachment 53085
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53085&action=edit
gzipped C++ source code
For the attached C code, recent gcc does this:
$ /home/dcb/gcc/results.20220528.asan.ubsan/bin/gcc -c -w -O1 bug469.cc
$ /home/dcb/gcc/results.20220604.asan.ubsan/bin/gcc -c -w -O1 bug469.cc
In file included from ../deps/v8/src/handles.h:8,
from ../deps/v8/src/builtins.h:9,
from ../deps/v8/src/builtins.cc:5:
../deps/v8/include/v8.h:8013:22: internal compiler error: Segmentation fault
0x1091949 crash_signal(int)
/home/dcb/gcc/working/gcc/../../trunk.git/gcc/toplev.cc:322
0x943705 tree_check(tree_node*, char const*, int, char const*, tree_code)
../../trunk.git/gcc/tree.h:3510
0x943705 instantiate_decl(tree_node*, bool, bool)
/home/dcb/gcc/working/gcc/../../trunk.git/gcc/cp/pt.cc:26483
0x95b8c5 instantiate_pending_templates(int)
/home/dcb/gcc/working/gcc/../../trunk.git/gcc/cp/pt.cc:26803
$
Seems to be broken again sometime between git hash 919822adc923b00e
and aec868578d851576.
I will have my usual go at reducing the code.
next reply other threads:[~2022-06-05 4:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 4:49 dcb314 at hotmail dot com [this message]
2022-06-05 5:01 ` [Bug c++/105852] [13 Regression] " pinskia at gcc dot gnu.org
2022-06-05 7:02 ` dcb314 at hotmail dot com
2022-06-05 21:09 ` sam at gentoo dot org
2022-06-05 21:10 ` sam at gentoo dot org
2022-06-06 12:53 ` ppalka at gcc dot gnu.org
2022-06-06 13:03 ` [Bug c++/105852] [11/12/13 " ppalka at gcc dot gnu.org
2022-06-06 15:08 ` slyfox at gcc dot gnu.org
2022-06-06 22:39 ` jason at gcc dot gnu.org
2022-06-08 20:38 ` cvs-commit at gcc dot gnu.org
2022-06-08 20:39 ` cvs-commit at gcc dot gnu.org
2022-06-08 21:31 ` cvs-commit at gcc dot gnu.org
2022-06-08 21:31 ` cvs-commit at gcc dot gnu.org
2022-06-13 12:52 ` rguenth at gcc dot gnu.org
2023-05-09 3:47 ` cvs-commit at gcc dot gnu.org
2023-05-09 3:51 ` cvs-commit 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-105852-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).