public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@linux.ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Andrew Burgess <aburgess@redhat.com>,
	Keith Seitz <keiths@redhat.com>
Cc: cel@linux.ibm.com
Subject: Re: [PATCH 1/2, ver2]  PowerPC, Fix-test-gdb.base-store.exp
Date: Mon, 30 Oct 2023 10:16:54 -0700	[thread overview]
Message-ID: <bf36b1af8730dafe75fd2a6e6999226209d35beb.camel@linux.ibm.com> (raw)
In-Reply-To: <62b44b45916ee898484992d57cc7bfa2ca0bc040.camel@de.ibm.com>

Ulrich, Andrew:

On Mon, 2023-10-30 at 16:44 +0000, Ulrich Weigand wrote:
> Andrew Burgess <aburgess@redhat.com> wrote:
> 
> > I think adding this to the commit message would be a great
> > improvement.
> > But also, you said:
> > 
> > > Now, as Carl fixed the PowerPC DWARF mapper to fix some test
> > > case regressions that showed up on POWER10, he added correct
> > > mappings for all registers including VSCR.  This then caused
> > > unwinding out of the signal trampoline to start working
> > > correctly, which in turn exposed the pre-existing infrun.c bug
> > > in handling signal call trampolines.
> > 
> > As part of the commit message at this point I'd like to see the
> > name of
> > at least one (if the number is small, I'd list them all though)
> > test(s)
> > that required this change in order to keep working correctly.
> 
> I believe this showed up in sigstep.exp, but Carl would know for
> sure.
> Carl, please update the commit message as requested by Andrew.

I have updated the commit message adding some of the additional detail
that Ulrch gave on the underlying issue.  The commit message now starts
with an overview of the initial issue to be fixed in store.exp followed
by a discussion of the underlying bug that was then exposed by test
sigstep.exp.  The commit message then goes on with the detailed
discussion of the fix for both issues.  Finally, it summarizes the
failures in both store.exp and sigstep.exp that are fixed.  Hopefully
this updated commit message clearly explains the two separate issues
that the patch addresses. 

Thanks for the feedback from Andrew and the help from Ulrich to improve
the commit message. I will post the update patch for your review.

                            Carl 

                              


  reply	other threads:[~2023-10-30 17:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 14:51 Carl Love
2023-10-12 14:58 ` [Patch 1/2] " Carl Love
2023-10-13 20:34   ` Keith Seitz
2023-10-13 21:00     ` Carl Love
2023-10-16 11:12       ` Ulrich Weigand
2023-10-16 14:31   ` Andrew Burgess
2023-10-16 15:51     ` Carl Love
2023-10-19 15:54       ` Carl Love
2023-10-24  8:50       ` Andrew Burgess
2023-10-24 16:05         ` Carl Love
2023-10-20 18:08     ` [PATCH 1/2, ver2] " Carl Love
2023-10-24  9:30       ` Andrew Burgess
2023-10-25 13:24         ` Ulrich Weigand
2023-10-30  9:45           ` Andrew Burgess
2023-10-30 16:44             ` Ulrich Weigand
2023-10-30 17:16               ` Carl Love [this message]
2023-10-30 17:25               ` [PATCH 1/2, ver3] " Carl Love
2023-11-06 18:24                 ` Carl Love
2023-11-08 10:54                 ` Andrew Burgess
2023-10-12 15:00 ` [PATCH 2/2] " Carl Love
2023-10-13 20:35   ` Keith Seitz
2023-10-13 21:00     ` Carl Love
2023-10-16 11:13       ` Ulrich Weigand
2023-10-16 14:36   ` Andrew Burgess
2023-10-16 15:51     ` Carl Love
2023-10-20 18:08     ` Carl Love
2023-10-24  8:53       ` Andrew Burgess

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=bf36b1af8730dafe75fd2a6e6999226209d35beb.camel@linux.ibm.com \
    --to=cel@linux.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).