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 3/4] gdb: Add new parser rule for structure field names
Date: Fri, 21 Dec 2018 16:38:00 -0000 [thread overview]
Message-ID: <87imzmsumm.fsf@tromey.com> (raw)
In-Reply-To: <cb6c1de899e25f5ec7c3283f7d495b84cb2e0fc4.1545172667.git.andrew.burgess@embecosm.com> (Andrew Burgess's message of "Tue, 18 Dec 2018 22:40:12 +0000")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> Introduces a new rule in c-exp.y for matching structure field names.
Andrew> This is a restructure in preparation for the next commit, this commit
Andrew> shouldn't result in any user visible changes.
Andrew> gdb/ChangeLog:
Andrew> * c-exp.y (field_name): New %token, and new rule.
Andrew> (exp): Replace uses of 'name' with 'field_name' where appropriate.
This is ok. Thanks.
Tom
next prev parent reply other threads:[~2018-12-21 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 23:25 [PATCH] gdb: Allow struct fields named double 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 [this message]
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
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=87imzmsumm.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