From: Richard Biener <richard.guenther@gmail.com>
To: Richard Sandiford <richard.sandiford@arm.com>,
Andrew Pinski via Gcc-patches <gcc-patches@gcc.gnu.org>,
Andrew Pinski <apinski@marvell.com>
Subject: Re: [PATCH 2/2] AARCH64: Turn off unwind tables for crtbeginT.o
Date: Tue, 25 Jul 2023 09:06:18 +0200 [thread overview]
Message-ID: <CAFiYyc1BLJzz-smWABKEM4-ryej62RYWNfOn2B2xcLCqEW-buQ@mail.gmail.com> (raw)
In-Reply-To: <mptlef5gv8l.fsf@arm.com>
On Mon, Jul 24, 2023 at 5:56 PM Richard Sandiford via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Andrew Pinski via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> > The problem -fasynchronous-unwind-tables is on by default for aarch64
> > We need turn it off for crt*.o because it would make __EH_FRAME_BEGIN__ point
> > to .eh_frame data from crtbeginT.o instead of the user-defined object
> > during static linking.
>
> Could you go into more details? Which user-defined object do you mean?
>
> I notice alpha has:
>
> # When GAS-generated unwind tables are created, they get created
> # after the __FRAME_END__ terminator, which causes an ld error.
> CRTSTUFF_T_CFLAGS = -fno-unwind-tables
>
> which I guess was a separate problem.
x86 has
# crtend*.o cannot be compiled without -fno-asynchronous-unwind-tables,
# because then __FRAME_END__ might not be the last thing in .eh_frame
# section.
>
> Thanks,
> Richard
next prev parent reply other threads:[~2023-07-25 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 1:06 [PATCH 1/2] Fix PR 110066: crash with -pg -static on riscv Andrew Pinski
2023-07-23 1:06 ` [PATCH 2/2] AARCH64: Turn off unwind tables for crtbeginT.o Andrew Pinski
2023-07-24 15:55 ` Richard Sandiford
2023-07-25 7:06 ` Richard Biener [this message]
2023-07-23 3:35 ` [PATCH 1/2] Fix PR 110066: crash with -pg -static on riscv Kito Cheng
2024-05-08 16:07 ` Andrew Pinski
2023-07-23 6:46 ` 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=CAFiYyc1BLJzz-smWABKEM4-ryej62RYWNfOn2B2xcLCqEW-buQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=apinski@marvell.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).