From: Luis Machado <lgustavo@codesourcery.com>
To: Luis Machado <lgustavo@codesourcery.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH/RFC] Refactor gdb.reverse/insn-reverse.c
Date: Thu, 26 Jan 2017 16:54:00 -0000 [thread overview]
Message-ID: <634bd9ac-86c7-a38e-b3a1-429e0a3d3754@codesourcery.com> (raw)
In-Reply-To: <0f3b832e-3255-9c02-2aeb-90014865f557@codesourcery.com>
On 01/26/2017 10:39 AM, Luis Machado wrote:
> On 01/25/2017 04:28 PM, Yao Qi wrote:
>> On 17-01-25 12:11:01, Luis Machado wrote:
>>> That is a reasonable assessment. insn-reverse.[c|exp] is redundant
>>> and IMO
>>> would benefit from renaming too.
>>>
>>> The support in "insn-support-<arch>.c means support for a set of
>>> instructions for this particular subsystem of gdb, therefore why i
>>> went with
>>> that name. Thinking about it further, instruction decoding support is
>>> the
>>> basis/foundation of reverse debugging, without which things would not
>>> work
>>> properly. But i may be overthinking. :-)
>>
>> Every test is about testing some sort of support. Breakpoint test is
>> about breakpoint support, tracepoint test is about tracepoint support.
>> We don't have to explicitly mention "support" in the test case name,
>> IMO.
>>
>> It is easy to relate "insn-reverse-<arch>.c" to "insn-reverse.c".
>> If you think "reverse" is redundant, "insn.c" and "insn-<arch>.c" is
>> acceptable to me too.
>>
>
> It is not terribly important. I've reverted to the original name
> (insn-reverse-<arch>.c), updated things to mention the new name and
> pushed this as 8b00c176168dc7b0d78d0dc1f7d42f915375dc4a.
>
> Patch attached.
>
> Thanks for reviewing,
> Luis
Forgot to effectively add the files. I'll fix this in a bit.
prev parent reply other threads:[~2017-01-26 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:11 Luis Machado
2017-01-24 16:20 ` Luis Machado
2017-01-25 16:10 ` Yao Qi
2017-01-25 16:50 ` Luis Machado
2017-01-25 17:44 ` Pedro Alves
2017-01-25 18:11 ` Luis Machado
2017-01-25 22:28 ` Yao Qi
2017-01-26 16:39 ` Luis Machado
2017-01-26 16:54 ` Luis Machado [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=634bd9ac-86c7-a38e-b3a1-429e0a3d3754@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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