Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: 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 17:34:00 -0000	[thread overview]
Message-ID: <4DF64A01.5030403@redhat.com> (raw)
In-Reply-To: <20110613171352.GY11563@sunsite.ms.mff.cuni.cz>

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.

> 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?

I thought that those ABIs were deprecated.  At which point I don't find
myself caring much.  Besides -- the RISC PLT formats don't adjust the
stack, so the "default" unwinding rule of looking at the return address
works.


r~


  reply	other threads:[~2011-06-13 17:34 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
2011-06-13 17:34     ` Richard Henderson [this message]
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=4DF64A01.5030403@redhat.com \
    --to=rth@redhat.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@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