From: Pedro Alves <palves@redhat.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] add gdbarch_in_function_epilogue_p hook for sparc64
Date: Wed, 04 Dec 2013 12:15:00 -0000 [thread overview]
Message-ID: <529F1CE0.2060000@redhat.com> (raw)
In-Reply-To: <8738m9j5de.fsf@oracle.com>
On 12/04/2013 10:08 AM, Jose E. Marchesi wrote:
>
> On 10/16/2013 03:18 PM, Jose E. Marchesi wrote:
> > Note that despite sparc_in_function_epilogue_p must work on both sparc32
> > and sparc64 the patch only installs the hook on sparc64 targets. This
> > is because I can't test it in sparc32.
>
> Can't sparc64 run sparc32 binaries? Something like -m32 ?
>
> Yes it can. But right now what I have is a 64bit-only userspace. I
> will hook gdbarch_in_function_epilogue_p on the sparc32 target as soon
> as I can test it properly.
Ah, OK.
> + RESTORE is almost always found in the delay slot of a branch
> + instruction that transfer control to the caller, such as JMPL.
"transfers".
I don't know enough sparc64 to be able to say anything intelligent
about the substance of the patch itself.
--
Pedro Alves
next prev parent reply other threads:[~2013-12-04 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 14:16 Jose E. Marchesi
2013-10-16 20:53 ` Sergio Durigan Junior
2013-10-17 11:33 ` Jose E. Marchesi
2013-12-03 11:58 ` Jose E. Marchesi
2013-12-03 19:03 ` Pedro Alves
2013-12-04 10:07 ` Jose E. Marchesi
2013-12-04 12:15 ` Pedro Alves [this message]
2013-12-04 12:22 ` Jose E. Marchesi
2014-01-29 15:31 ` Jose E. Marchesi
2014-02-06 14:24 ` Jose E. Marchesi
2014-02-08 3:01 ` Joel Brobecker
2014-02-10 12:37 ` Jose E. Marchesi
2014-02-10 15:08 ` Mark Kettenis
2014-02-10 15:23 ` Jose E. Marchesi
2013-12-04 17:02 ` Joel Brobecker
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=529F1CE0.2060000@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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