Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org,  Tom Tromey <tom@tromey.com>,
		Simon Marchi <simark@simark.ca>,
		jimw@sifive.com, 	jhb@FreeBSD.org, 	palmer@sifive.com
Subject: Re: [PATCHv2 4/4] gdb: Allow struct fields named double
Date: Fri, 21 Dec 2018 17:19:00 -0000	[thread overview]
Message-ID: <87efaasspe.fsf@tromey.com> (raw)
In-Reply-To: <41fdb503cf18c86986aaf70dd2387c42f52502ee.1545172667.git.andrew.burgess@embecosm.com>	(Andrew Burgess's message of "Tue, 18 Dec 2018 22:40:13 +0000")

>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:

Andrew> gdb/ChangeLog:

Andrew> 	* c-exp.y (field_name): Allow DOUBLE_KEYWORD, INT_KEYWORD, LONG,
Andrew> 	SHORT, SIGNED_KEYWORD, and UNSIGNED tokens to act as a field
Andrew> 	names.
Andrew> 	(typename_stoken): New function.

Andrew> gdb/testsuite/ChangeLog:

Andrew> 	* gdb.dwarf2/dw2-unusual-field-names.c: New file.
Andrew> 	* gdb.dwarf2/dw2-unusual-field-names.exp: New file.

Thanks for doing this.  This is ok.  I wanted to mention that I think
it's a good idea to do this because the C language also serves as a
fallback either when language support isn't available or when one wants
to inspect things in a low-level way, and in this case it can be useful
to have some extensions to C.

Andrew> +foreach field_name { double float char byte long int short unsigned signed } {
Andrew> +    run_test $field_name
Andrew> +}

I'd like to verify that there aren't any duplicate test names resulting
from this approach.  If there aren't, this is fine; if there are, I
think run_test could be wrapped in a with_test_prefix.

thanks,
Tom


  reply	other threads:[~2018-12-21 17:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 23:25 [PATCH] " Andrew Burgess
2018-12-16 16:23 ` Simon Marchi
2018-12-16 16:42   ` Tom Tromey
2018-12-18 22:40     ` [PATCHv2 0/4] " Andrew Burgess
2018-12-24 17:30       ` Andrew Burgess
2018-12-18 22:40     ` [PATCHv2 3/4] gdb: Add new parser rule for structure field names Andrew Burgess
2018-12-21 16:38       ` Tom Tromey
2018-12-18 22:40     ` [PATCHv2 1/4] gdb: Extend the comments in c-exp.y Andrew Burgess
2018-12-21 15:44       ` Tom Tromey
2018-12-18 22:40     ` [PATCHv2 4/4] gdb: Allow struct fields named double Andrew Burgess
2018-12-21 17:19       ` Tom Tromey [this message]
2018-12-18 22:40     ` [PATCHv2 2/4] gdb: Resolve 49 reduce/reduce conflicts in c-exp.y Andrew Burgess
2018-12-21 16:37       ` Tom Tromey

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=87efaasspe.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=jimw@sifive.com \
    --cc=palmer@sifive.com \
    --cc=simark@simark.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