From: Jakub Jelinek <jakub@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: 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 17:14:00 -0000 [thread overview]
Message-ID: <20110613171352.GY11563@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <4DF23519.7050607@twiddle.net>
On Fri, Jun 10, 2011 at 08:15:37AM -0700, Richard Henderson wrote:
> On 06/10/2011 12:45 AM, Jakub Jelinek wrote:
> > Anyway, I think hardcoding this in the linker would be problematic,
> > we couldn't tweak it, so providing some special hidden symbols around
> > the .plt section and let glibc crtfiles provide it sounds like the best
> > option to me.
>
> Would it be problematic beyond the fact that it's easier to write the
> directives in assembler than it is within bfd?
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)?
On other targets like SPARC or PowerPC -mbss-plt it is the dynamic linker
which updates or completely writes .plt section though, should in that
case the dynamic linker provide the unwind info instead?
> As for the actual unwind info, I agree that using pointer arithmetic
> is the better expression over decoding the insns. Increasing the
> alignment is probably a good idea, also for the actual decoding of
> the insns on the real hardware.
Ok.
Jakub
next prev parent reply other threads:[~2011-06-13 17:14 UTC|newest]
Thread overview: 7+ 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 [this message]
2011-06-13 17:34 ` Richard Henderson
2011-06-13 20:54 ` Ian Lance Taylor
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=20110613171352.GY11563@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=mjw@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