Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: cole945@gmail.com (Wei-cheng Wang), brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3 v4] Process record support for PowerPC
Date: Sat, 17 Jan 2015 11:47:00 -0000	[thread overview]
Message-ID: <201501171146.t0HBktpk008932@d03av02.boulder.ibm.com> (raw)
In-Reply-To: <CAPmZyH6Gp2xan6anM9hAGir72_kPDopXjg0PaoAaQ+0af+J8PA@mail.gmail.com> from "Wei-cheng Wang" at Jan 17, 2015 02:02:24 PM

Wei-cheng Wang wrote:

> I've got the commit access.
> Ok to commit now? :)
> 
> [1/3] Epilogue unwinder for PowerPC
> https://sourceware.org/ml/gdb-patches/2014-12/msg00165.html
> [2/3] Reverse debugging for PowerPC
> https://sourceware.org/ml/gdb-patches/2014-12/msg00629.html
> [3/3] Skip-trampoline for reverse-stepping
> https://sourceware.org/ml/gdb-patches/2014-12/msg00487.html

Excellent!  Please go ahead and commit those patches to mainline.

Unfortunately, in the meantime GDB 7.9 has already branched.  It would
be really good to have those patches in the branch as well.

Joel, given that the patches would have been ready before the branch
date, except for the delay to get the FSF assignment in place, would
it be OK with you to backport the patch set to the branch as well?

The patch set does not touch non-PowerPC code at all, and even within
PowerPC code, there should be only minimal effect unless you're actually
using the process record feature.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2015-01-17 11:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-06 18:00 [PATCH 2/3 v2] " Wei-cheng Wang
2014-12-08 19:12 ` Ulrich Weigand
2014-12-17 17:07   ` [PATCH 2/3 v3] " Wei-cheng Wang
2014-12-17 18:41     ` Ulrich Weigand
2014-12-25 17:27       ` [PATCH 2/3 v4] " Wei-cheng Wang
2015-01-01 14:19         ` Ulrich Weigand
2015-01-04 16:27           ` Wei-cheng Wang
2015-01-06 12:42             ` Ulrich Weigand
2015-01-17  6:02               ` Wei-cheng Wang
2015-01-17 11:47                 ` Ulrich Weigand [this message]
2015-01-17 18:53                   ` Joel Brobecker
2015-01-17 21:20                     ` Broken build: rs6000-tdep.c: 32-bit host --enable-targets=all --enable-64-bit-bfd [Re: [PATCH 2/3 v4] Process record support for PowerPC] Jan Kratochvil
2015-01-18  4:47                       ` Wei-cheng Wang
2015-01-18  7:01                         ` Jan Kratochvil
2015-01-18  8:01                           ` Wei-cheng Wang
2015-01-19  7:48                             ` Joel Brobecker
2015-01-19 16:10                               ` [PATCH 2/3 v4] Process record support for PowerPC Wei-cheng Wang
2015-01-19 18:05                                 ` Ulrich Weigand
2015-01-20 16:03                                   ` Wei-cheng Wang
2015-01-20 18:14                                     ` Ulrich Weigand
2015-01-26 17:19                                       ` Ulrich Weigand
2015-01-26 17:19                                         ` Wei-cheng Wang
2015-01-26 19:16                                           ` Doug Evans
2015-01-26 20:29                                             ` Doug Evans

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=201501171146.t0HBktpk008932@d03av02.boulder.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=cole945@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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