public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Wei-cheng Wang <cole945@gmail.com>
To: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5 v4] Tracepoint for ppc64.
Date: Sun, 28 Jun 2015 06:21:00 -0000	[thread overview]
Message-ID: <CAPmZyH4SWQsfQjx-qyT-gc2hC0i6K1GQvP6-PHBFMdRuoMS6xg@mail.gmail.com> (raw)
In-Reply-To: <1435422102-39438-4-git-send-email-cole945@gmail.com>

Hi,

I forgot to mention two more things.

A new function (gdbserver target op), ppc_get_thread_area, is implemented
used for the jump pad lock object (collecting_t). Please have a look.

Changing timeout in tspeed.exp is reverted in this patch.  Recently I
tested the patch on gcc112 server and timeout should be 540 instead of 360
in order to pass tspeed.exp.  I am not sure what's the proper value for timeout.
Maybe someone will test it in another environment, and 540 is not enough again.

Thanks,
Wei-cheng

  reply	other threads:[~2015-06-28  6:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27 16:21 [PATCH 1/5 v4] Remove tracepoint_action ops Wei-cheng Wang
2015-06-27 16:22 ` [PATCH 5/5 v4] Allow target to decide where to map jump-pad Wei-cheng Wang
2015-07-03 16:38   ` Ulrich Weigand
2015-06-27 16:22 ` [PATCH 4/5 v4] Tracepoint for ppc64 Wei-cheng Wang
2015-06-28  6:21   ` Wei-cheng Wang [this message]
2015-06-29 15:54   ` Pierre Langlois
2015-07-03 16:37   ` Ulrich Weigand
2015-06-27 16:22 ` [PATCH 3/5 v4] Fix argument to compiled_cond, and add cases for compiled-condition Wei-cheng Wang
2015-06-30  9:57   ` Pedro Alves
2015-09-14 14:04   ` Pierre Langlois
2015-09-16 16:15   ` Yao Qi
2015-06-27 16:22 ` [PATCH 2/5 v4] powerpc: Support z-point type in gdbserver Wei-cheng Wang
2015-07-03 15:17   ` Ulrich Weigand
2016-02-24 12:05   ` Marcin Kościelnicki
2016-02-24 17:37     ` Ulrich Weigand
2016-02-24 17:39       ` Marcin Kościelnicki
2015-06-30  9:57 ` [PATCH 1/5 v4] Remove tracepoint_action ops Pedro Alves

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=CAPmZyH4SWQsfQjx-qyT-gc2hC0i6K1GQvP6-PHBFMdRuoMS6xg@mail.gmail.com \
    --to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).