Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>,
	Richard Biener <rguenther@suse.de>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] Speedup lnp_state_machine::handle_special_opcode
Date: Thu, 13 Feb 2020 18:26:00 -0000	[thread overview]
Message-ID: <d5a8288a-8935-a091-618d-7da276047eeb@redhat.com> (raw)
In-Reply-To: <c070bca3-5443-af6c-f003-373151e5be00@suse.de>

Arguably the the compiler should do this for us.  *cough*  :-)

On 2/13/20 2:23 PM, Tom de Vries wrote:
> On 13-02-2020 14:03, Richard Biener wrote:
>> Care to pick up this one-time patch without myself becoming familiar
>> with gdb testing & patch submission?
> 
> Of course.  Added ChangeLog entry, build and reg-tested on x86_64-linux.

The ChangeLog entry (as well a git author) should reflect the patch's
authorship.

Otherwise OK.

Thanks,
Pedro Alves


  reply	other threads:[~2020-02-13 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 13:03 Richard Biener
2020-02-13 14:23 ` Tom de Vries
2020-02-13 18:26   ` Pedro Alves [this message]
2020-02-14  7:39     ` Tom de Vries

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=d5a8288a-8935-a091-618d-7da276047eeb@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rguenther@suse.de \
    --cc=tdevries@suse.de \
    /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