public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/106261] [10/11/12/13 Regression] ICE in output_call_frame_info, at dwarf2out.cc:943
Date: Wed, 27 Jul 2022 10:06:57 +0000 [thread overview]
Message-ID: <bug-106261-4-UXdTeYIVyZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106261-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106261
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:f9671b60f9395cb1dca128b92f5dd215f5aeaae1
commit r13-1856-gf9671b60f9395cb1dca128b92f5dd215f5aeaae1
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Jul 27 12:06:22 2022 +0200
cgraphunit: Don't emit asm thunks for -dx [PR106261]
When -dx option is used (didn't know we have it and no idea what is it
useful for), we just expand functions to RTL and then omit all further
RTL passes, so the normal functions aren't actually emitted into assembly,
just variables.
The following testcase ICEs, because we don't emit the methods, but do
emit thunks pointing to that and those thunks have unwind info and rely on
at least some real functions to be emitted (which is normally the case,
thunks are only emitted for locally defined functions) because otherwise
there are no CIEs, only FDEs and dwarf2out is upset about it.
The following patch fixes that by not emitting assembly thunks for -dx
either.
2022-07-27 Jakub Jelinek <jakub@redhat.com>
PR debug/106261
* cgraphunit.cc (cgraph_node::assemble_thunks_and_aliases): Don't
output asm thunks for -dx.
* g++.dg/debug/pr106261.C: New test.
next prev parent reply other threads:[~2022-07-27 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 18:59 [Bug c++/106261] New: " gscfq@t-online.de
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 [this message]
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-UXdTeYIVyZ@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).