From: Andreas Schwab <schwab@suse.de>
To: Michael Matz <matz@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc-patches@gcc.gnu.org,
Richard Biener <richard.guenther@gmail.com>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] lto: pass through -funwind-tables and -fasynchronous-unwind-tables
Date: Wed, 18 Jan 2023 17:09:53 +0100 [thread overview]
Message-ID: <mvm5yd3ygby.fsf@suse.de> (raw)
In-Reply-To: <alpine.LSU.2.20.2301181522420.30340@wotan.suse.de> (Michael Matz's message of "Wed, 18 Jan 2023 15:32:00 +0000 (UTC)")
On Jan 18 2023, Michael Matz wrote:
> The purest solution is to emit unwind tables for all functions that
> request it into .eh_frame and for those that don't request it put
> into .debug_frame (if also -g is on).
The assembler does not allow switching back to .eh_frame once a
different format has been chosen, so .eh_frame must be either on or off
all the way through.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-01-18 16:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 10:16 Andreas Schwab
2023-01-18 11:05 ` Richard Biener
2023-01-18 11:25 ` Andreas Schwab
2023-01-18 11:31 ` Jakub Jelinek
2023-01-18 12:30 ` Andreas Schwab
2023-01-18 12:35 ` Jakub Jelinek
2023-01-18 12:39 ` Andreas Schwab
2023-01-18 12:47 ` Jakub Jelinek
2023-01-18 13:00 ` Andreas Schwab
2023-01-18 14:03 ` Michael Matz
2023-01-18 14:14 ` Andreas Schwab
2023-01-18 14:25 ` Jakub Jelinek
2023-01-18 15:11 ` Andreas Schwab
2023-01-18 14:27 ` Jakub Jelinek
2023-01-18 15:09 ` Andreas Schwab
2023-01-18 15:11 ` Jakub Jelinek
2023-01-18 15:16 ` Michael Matz
2023-01-18 15:19 ` Jakub Jelinek
2023-01-18 15:32 ` Michael Matz
2023-01-18 16:09 ` Andreas Schwab [this message]
2023-01-18 16:25 ` Jan Hubicka
2023-01-18 16:28 ` Jakub Jelinek
2023-01-18 15:07 ` Jan Hubicka
2023-01-19 7:14 ` Richard Biener
2023-01-18 13:36 ` Andreas Schwab
2023-01-25 13:16 ` Richard Biener
2023-01-25 13:50 ` Andreas Schwab
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=mvm5yd3ygby.fsf@suse.de \
--to=schwab@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=matz@suse.de \
--cc=richard.guenther@gmail.com \
/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).