From: "Andrew Burgess" <aburgess@broadcom.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: Add fullname field in disassembly output
Date: Wed, 07 Nov 2012 15:08:00 -0000 [thread overview]
Message-ID: <509A7960.3010306@broadcom.com> (raw)
In-Reply-To: <83d2zq39un.fsf@gnu.org>
On 06/11/2012 5:44 PM, Eli Zaretskii wrote:
>> Date: Tue, 6 Nov 2012 12:13:36 +0000
>> From: "Andrew Burgess" <aburgess@broadcom.com>
>> cc: gdb-patches@sourceware.org, "Eli Zaretskii" <eliz@gnu.org>
>>
>
> The patch for the manual is OK with these changes.
Thanks for the review, I'll make those changes.
>
>> +file="../../../src/gdb/testsuite/gdb.mi/basics.c",
>> +fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
>> +line_asm_insn=[@{address="0x000107bc",
>> +func-name="main",offset="0",inst="save %sp, -112, %sp"@}]@},
>> src_and_asm_line=@{line="32",
>> -file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \
>> - testsuite/gdb.mi/basics.c",line_asm_insn=[
>> -@{address="0x000107c0",func-name="main",offset="4",
>> -inst="mov 2, %o0"@},
>> +file="../../../src/gdb/testsuite/gdb.mi/basics.c",
>> +fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
>> +line_asm_insn=[@{address="0x000107c0",
>> +func-name="main",offset="4",inst="mov 2, %o0"@},
>> @{address="0x000107c4",func-name="main",offset="8",
>> inst="sethi %hi(0x11800), %o2"@}]@}]
>> (gdb)
>
> Why do we sometimes use names with a hyphen, like func-name, and
> sometimes with underscores, like line_asm_insn? Shouldn't we pick one
> and use it consistently?
That would probably be a good thing, but given I didn't add the code I'd
rather not start changing these things. Also, given that this exists in
the wild and the MI interface is supposed to remain consistent I suspect
we're stuck with what we have...
Just so I'm clear, should I consider this a block to committing this patch?
Thanks,
Andrew
next prev parent reply other threads:[~2012-11-07 15:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 16:09 [PATCH] Display full file path in MI style disassembly listing Andrew Burgess
2012-10-05 12:44 ` Jan Kratochvil
2012-10-07 14:28 ` Andrew Burgess
2012-10-07 14:34 ` Jan Kratochvil
2012-10-07 15:16 ` Joel Brobecker
2012-10-17 17:20 ` Tom Tromey
2012-10-17 18:13 ` Pedro Alves
2012-10-18 6:48 ` Jan Kratochvil
2012-10-18 9:49 ` Andrew Burgess
2012-10-18 10:17 ` Pedro Alves
2012-10-18 18:06 ` André Pönitz
2012-10-18 13:45 ` Jan Kratochvil
2012-10-17 17:16 ` Tom Tromey
2012-10-18 9:34 ` Andrew Burgess
2012-10-18 13:45 ` Jan Kratochvil
2012-10-17 18:25 ` Pedro Alves
2012-10-22 21:26 ` Add fullname field in disassembly output (Was Re: [PATCH] Display full file path in MI style disassembly listing) Andrew Burgess
2012-10-31 14:54 ` Add fullname field in disassembly output Pedro Alves
2012-11-02 10:59 ` Andrew Burgess
2012-11-02 15:32 ` Pedro Alves
2012-11-06 12:14 ` Andrew Burgess
2012-11-06 17:44 ` Eli Zaretskii
2012-11-07 15:08 ` Andrew Burgess [this message]
2012-11-07 15:48 ` Pedro Alves
2012-11-08 21:30 ` Tom Tromey
2012-11-09 13:26 ` Andrew Burgess
2012-11-03 7:42 ` Eli Zaretskii
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=509A7960.3010306@broadcom.com \
--to=aburgess@broadcom.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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