From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/fortran: add parser support for lbound and ubound
Date: Tue, 09 Feb 2021 13:42:39 -0700 [thread overview]
Message-ID: <8735y5as74.fsf@tromey.com> (raw)
In-Reply-To: <20210209165228.2060061-1-andrew.burgess@embecosm.com> (Andrew Burgess's message of "Tue, 9 Feb 2021 16:52:28 +0000")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> Add support for the LBOUND and UBOUND built in functions to the
Andrew> Fortran expression parser.
I really should have finished that expression series sooner.
Andrew> +%token <opcode> UNOP_OR_BINUP_INTRINSIC
Why "binup" and not "binop"?
Looks reasonable to me otherwise.
Tom
prev parent reply other threads:[~2021-02-09 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 16:52 Andrew Burgess
2021-02-09 20:42 ` Tom Tromey [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=8735y5as74.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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).