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++/106261] New: ICE in output_call_frame_info, at dwarf2out.cc:943 Date: Mon, 11 Jul 2022 18:59:26 +0000 [thread overview] Message-ID: <bug-106261-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106261 Bug ID: 106261 Summary: ICE in output_call_frame_info, at dwarf2out.cc:943 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: --- Affects versions down to at least r5, with file g++.dg/torture/pr60871.C : $ gcc-13-20220710 -c pr60871.C -dx -fno-dwarf2-cfi-asm pr60871.C:33:28: internal compiler error: Segmentation fault 33 | void fn1 () { F::m_fn2 (); } | ^ 0x10ecfef crash_signal ../../gcc/toplev.cc:322 0xc33a42 vec<dw_cfi_node*, va_gc, vl_embed>::iterate(unsigned int, dw_cfi_node**) const ../../gcc/vec.h:930 0xc33a42 output_call_frame_info ../../gcc/dwarf2out.cc:943
next reply other threads:[~2022-07-11 18:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-11 18:59 gscfq@t-online.de [this message] 2022-07-11 19:58 ` [Bug debug/106261] " marxin at gcc dot gnu.org 2022-07-11 21:12 ` pinskia at gcc dot gnu.org 2022-07-11 21:14 ` [Bug debug/106261] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-07-12 6:36 ` rguenth at gcc dot gnu.org 2022-07-26 14:15 ` jakub at gcc dot gnu.org 2022-07-27 10:06 ` cvs-commit at gcc dot gnu.org 2022-07-27 10:47 ` [Bug debug/106261] [10/11/12 " jakub at gcc dot gnu.org 2022-07-30 9:34 ` cvs-commit at gcc dot gnu.org 2022-07-30 10:09 ` [Bug debug/106261] [10/11 " jakub at gcc dot gnu.org 2022-11-04 8:30 ` cvs-commit at gcc dot gnu.org 2022-11-04 11:00 ` [Bug debug/106261] [10 " jakub at gcc dot gnu.org 2023-05-03 15:18 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:19 ` 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-106261-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: linkBe 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).