From: Carl Love <cel@us.ibm.com>
To: Guinevere Larsen <blarsen@redhat.com>,
Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org,
UlrichWeigand <Ulrich.Weigand@de.ibm.com>,
pedro@palves.net
Cc: luis.machado@arm.com, cel@us.ibm.com
Subject: RE: [PATCH 0/2] Fix reverse stepping multiple contiguous PC ranges over the line table.
Date: Mon, 25 Sep 2023 15:15:20 -0700 [thread overview]
Message-ID: <7c249dcf83fa859550685675becd7dc4205d1f16.camel@us.ibm.com> (raw)
In-Reply-To: <899d12bd464b803a2d95d0787243a825550069a3.camel@us.ibm.com>
GDB maintainers:
Ping.
On Tue, 2023-09-05 at 08:12 -0700, Carl Love wrote:
> GDB maintainers:
>
> Ping. I was wondering if anyoneany of the maintainers has had time
> to
> review these patches? Thanks for your time and effort on the patch.
>
> On Tue, 2023-08-29 at 11:55 -0700, Carl Love wrote:
> > Guinevere:
> >
> > On Tue, 2023-08-29 at 14:28 +0200, Guinevere Larsen wrote:
> > > I have tested this patch with both GCC and Clang. I can verify it
> > > fixes
> > > the issue, adds no regression, and even fixes the final issues
> > > when
> > > testing gdb.reverse with clang!
> > >
> > > Tested-By: Guinevere Larsen <blarsen@redhat.com>
>
> Carl
next prev parent reply other threads:[~2023-09-25 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 15:50 Carl Love
2023-08-25 15:53 ` [PATCH 1/2] Add gdb_compile options column-info and no-column-info Carl Love
2023-08-25 15:57 ` [PATCH 2/2 ver 8] Fix reverse stepping multiple contiguous PC ranges over the line table Carl Love
2023-08-29 12:28 ` [PATCH 0/2] " Guinevere Larsen
2023-08-29 18:55 ` Carl Love
2023-09-05 15:12 ` Carl Love
2023-09-25 22:15 ` Carl Love [this message]
2023-11-02 17:30 ` PING " Carl Love
-- strict thread matches above, loose matches on Subject: below --
2023-08-07 18:54 Carl Love
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=7c249dcf83fa859550685675becd7dc4205d1f16.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
/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).