From: Jan Hubicka <hubicka@ucw.cz>
To: Andreas Schwab <schwab@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] lto: pass through -funwind-tables and -fasynchronous-unwind-tables
Date: Wed, 18 Jan 2023 16:07:12 +0100 [thread overview]
Message-ID: <Y8gLIJTOxL2zI0v9@kam.mff.cuni.cz> (raw)
In-Reply-To: <mvmtu0oxajh.fsf@suse.de>
> No unwind tables are generated, as if -funwind-tables is ignored. If
> LTO is disabled, everything works as expected.
I think it is because dwaf2out_do_eh_frame is called out of function
context at the end of compilation. At that time cfun is NULL
and the flag is read from global settings that are wrong.
So we need to bookkeep if we saw function that needs EH tables and not.
Honza
>
> --
> 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 15:07 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
2023-01-18 16:25 ` Jan Hubicka
2023-01-18 16:28 ` Jakub Jelinek
2023-01-18 15:07 ` Jan Hubicka [this message]
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=Y8gLIJTOxL2zI0v9@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=schwab@suse.de \
/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).