From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <palves@redhat.com>,
Richard Biener <rguenther@suse.de>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Speedup lnp_state_machine::handle_special_opcode
Date: Fri, 14 Feb 2020 07:39:00 -0000 [thread overview]
Message-ID: <c3a465f7-94e4-4ebe-4918-b31f93b7235a@suse.de> (raw)
In-Reply-To: <d5a8288a-8935-a091-618d-7da276047eeb@redhat.com>
On 13-02-2020 19:26, Pedro Alves wrote:
> 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.
>
Committed with those change @
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=258bf0ee3748d4354e13daf00f02266cafa96389
.
Thanks,
- Tom
prev parent reply other threads:[~2020-02-14 7:39 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
2020-02-14 7:39 ` Tom de Vries [this message]
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=c3a465f7-94e4-4ebe-4918-b31f93b7235a@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=rguenther@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