From: Pedro Alves <palves@redhat.com>
To: Wei-cheng Wang <cole945@gmail.com>,
uweigand@de.ibm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Fast tracepoint for powerpc64le
Date: Wed, 04 Mar 2015 17:22:00 -0000 [thread overview]
Message-ID: <54F73F32.6070102@redhat.com> (raw)
In-Reply-To: <54E77725.2070707@gmail.com>
On 02/20/2015 06:04 PM, Wei-cheng Wang wrote:
> +/* Return the value of register REGNUM. RAW_REGS is collected buffer
> + by jump pad. This function is called by emit_reg. */
> +
> +ULONGEST __attribute__ ((visibility("default"), used))
> +gdb_agent_get_raw_reg (const unsigned char *raw_regs, int regnum)
> +{
> + if (regnum >= PPC_NUM_FT_COLLECT_GREGS)
Meanwhile several C++ patches landed which changed how this
function should be declared. Please make this:
IP_AGENT_EXPORT_FUNC ULONGEST
gdb_agent_get_raw_reg (const unsigned char *raw_regs, int regnum)
{
I think it'd be good to split out the changes that make
ppc gdbserver do Z0 packets too.
(nit: it'd make it easier to identify the different patches in
the series if they had different subjects, which identified their
actual contents. That's ideal for the subjects of the git commits
too, so best do that when submitting the patches already.)
Thanks for working on this!
Pedro Alves
prev parent reply other threads:[~2015-03-04 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 18:04 Wei-cheng Wang
2015-02-25 15:20 ` [PATCH 1/3 v2] " Wei-cheng Wang
2015-03-17 13:34 ` Ulrich Weigand
2015-03-29 19:27 ` Wei-cheng Wang
2015-04-08 16:49 ` Ulrich Weigand
2015-02-27 19:53 ` [PATCH 1/2] " Ulrich Weigand
2015-03-01 17:42 ` Wei-cheng Wang
2015-03-17 13:48 ` Ulrich Weigand
2015-03-04 17:13 ` Pedro Alves
2015-03-17 18:12 ` Ulrich Weigand
2015-03-17 19:03 ` Pedro Alves
2015-03-18 11:04 ` Ulrich Weigand
2015-03-18 16:07 ` Pedro Alves
2015-03-18 16:53 ` Ulrich Weigand
2015-03-04 17:22 ` Pedro Alves [this message]
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=54F73F32.6070102@redhat.com \
--to=palves@redhat.com \
--cc=cole945@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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