From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: jose.marchesi@oracle.com, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] [SPARC64] Figure out where a longjmp will land
Date: Sun, 20 Oct 2013 19:27:00 -0000 [thread overview]
Message-ID: <201310201926.r9KJQlD4017034@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20131017055736.GC3302@adacore.com> (message from Joel Brobecker on Thu, 17 Oct 2013 09:57:36 +0400)
> Date: Thu, 17 Oct 2013 09:57:36 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> > 2013-10-08 Jose E. Marchesi <jose.marchesi@oracle.com>
> >
> > * sparc-tdep.c (sparc_is_annulled_branch_insn): New function.
> > * sparc-tdep.h: And its prototype.
> >
> > * sparc64-linux-tdep.c (sparc64_linux_get_longjmp_target): New
> > function.
> > (sparc64_linux_init_abi): Register the get_longjmp_target hook.
>
> This looks reasonable to me, with a minor correction requested below.
> But Sparc patches normally get reviewed by MarkK, so can you give it
> another week before checking the final version in? (remember that
> when you check something in that is different from the patch already
> posted, an updated patch should be sent to the list, for the record).
Well, for the Linux-specific bits it is a good idea to make sure that
David S. Miller sees the changes as well.
next prev parent reply other threads:[~2013-10-20 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 17:25 Jose E. Marchesi
2013-10-08 20:23 ` Tom Tromey
2013-10-08 20:49 ` Sergio Durigan Junior
2013-10-08 21:51 ` Jose E. Marchesi
2013-10-17 5:57 ` Joel Brobecker
2013-10-17 11:31 ` Jose E. Marchesi
2013-10-20 19:32 ` Mark Kettenis
2013-10-21 12:52 ` Jose E. Marchesi
2013-10-20 19:27 ` Mark Kettenis [this message]
2013-10-21 12:53 ` Jose E. Marchesi
2013-10-22 8:22 ` Mark Kettenis
2013-11-18 14:02 ` Jose E. Marchesi
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=201310201926.r9KJQlD4017034@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=tromey@redhat.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