From: "Maciej W. Rozycki" <macro@mips.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
<gdb-patches@sourceware.org>, <binutils@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>,
Fredrik Noring <noring@nocrew.org>
Subject: Re: [PATCH v4] GDB PR tdep/8282: MIPS: Wire in `set disassembler-options'
Date: Thu, 21 Jun 2018 18:29:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1806211914250.20622@tp.orcam.me.uk> (raw)
In-Reply-To: <3bd95a5f-e43e-2efe-e261-c2cf30d06d14@ericsson.com>
Hi Simon,
> This patch looks good from the GDB side (with one nit in the test below), but
> somebody from binutils would need to review the bits in opcodes/include.
Yes, that's why I requested it separately and posted to both mailing
lists.
> > +# Verify ABI overrides.
> > +mips_disassemble_test bar "move\t\\\$2,\\\$8" "disassemble ABI (numeric)"
> > +gdb_test "set disassembler-options"
> > +gdb_test "set mips abi o32"
> > +mips_disassemble_test bar "move\tv0,t0" "disassemble ABI (o32)"
> > +gdb_test "set mips abi n32"
> > +mips_disassemble_test bar "move\tv0,a4" "disassemble ABI (n32)"
> > +gdb_test "set mips abi n64"
> > +mips_disassemble_test bar "move\tv0,a4" "disassemble ABI (n64)"
>
> Avoid parenthesis at the end of test names:
>
> https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Do_not_use_.22tail_parentheses.22_on_test_messages
Thanks for the pointer. Although it makes sense to me at first glance
that's quite a recent change to a long-established practice. Perhaps it
could have been avoided by coding the regression analysis tools referred
more carefully, but I won't be questioning the decision at this point.
The wiki does not indicate a suggested replacement however and I would
rather avoid creating a mess where individual tests would use different
approaches. Offhand I'd be inclined to use brackets, either square or
angled. What has been the new practice then?
Maciej
next prev parent reply other threads:[~2018-06-21 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 7:27 Maciej W. Rozycki
2018-06-21 17:52 ` Simon Marchi
2018-06-21 18:29 ` Maciej W. Rozycki [this message]
2018-06-21 19:19 ` Simon Marchi
2018-06-21 19:56 ` Maciej W. Rozycki
2018-06-21 20:06 ` Simon Marchi
2018-06-29 14:37 ` [PING][PATCH " Maciej W. Rozycki
2018-06-29 14:41 ` Maciej W. Rozycki
2018-07-02 15:57 ` Nick Clifton
2018-07-02 23:01 ` [committed v5] " Maciej W. Rozycki
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=alpine.DEB.2.00.1806211914250.20622@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=noring@nocrew.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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).