From: Ian Lance Taylor <iant@google.com>
To: Richard Henderson <rth@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Richard Henderson <rth@twiddle.net>,
libc-alpha@sourceware.org, binutils@sourceware.org,
gdb@sourceware.org, Mark Wielaard <mjw@redhat.com>,
Frank Eigler <fche@redhat.com>
Subject: Re: RFC: Unwind info for PLT
Date: Mon, 13 Jun 2011 20:53:00 -0000 [thread overview]
Message-ID: <mcrei2xtpv1.fsf@coign.corp.google.com> (raw)
In-Reply-To: <4DF64A01.5030403@redhat.com> (Richard Henderson's message of "Mon, 13 Jun 2011 10:33:53 -0700")
Richard Henderson <rth@redhat.com> writes:
> On 06/13/2011 10:13 AM, Jakub Jelinek wrote:
>> Yeah, easier to write and easier to change. Anyway, if you prefer to do
>> it in ld, I can try to do it there. Just a question, should it be done
>> unconditionally, or guarded with some ld cmdline option (either existing one, like
>> abuse --eh-frame-hdr for it, or a new one)?
>
> I don't have a real preference. I could see abusing --eh-frame-hdr makes sense.
I believe the default should be to generate the additional new unwind
information. The only people who would not want it would be people who
want to minimize their binary size. I also don't think this has
anything to do with --eh-frame-hdr, which simply directs the linker to
create a PT_GNU_EH_FRAME program header. So I think there should be a
new linker option to *not* generate unwind info, and we should have
-fno-unwind-tables pass that option to a linker which understands it.
Ian
next prev parent reply other threads:[~2011-06-13 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 7:45 Jakub Jelinek
2011-06-10 14:11 ` Mark Kettenis
2011-06-10 14:17 ` Joseph S. Myers
2011-06-10 15:15 ` Richard Henderson
2011-06-13 17:14 ` Jakub Jelinek
2011-06-13 17:34 ` Richard Henderson
2011-06-13 20:53 ` Ian Lance Taylor [this message]
2011-06-14 20:19 ` Jakub Jelinek
2011-06-20 9:32 ` [PATCH] Unwind info for PLT on i?86/x86_64 Jakub Jelinek
2011-06-20 12:21 ` Richard Henderson
2011-06-20 13:03 ` H.J. Lu
2011-06-20 17:14 ` H.J. Lu
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=mcrei2xtpv1.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=jakub@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mjw@redhat.com \
--cc=rth@redhat.com \
--cc=rth@twiddle.net \
/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).