From: Tom Tromey <tom@tromey.com>
To: Richard Bunt via Gdb-patches <gdb-patches@sourceware.org>
Cc: agontarek@nvidia.com, Richard Bunt <richard.bunt@linaro.org>
Subject: Re: [PATCH v1] gdb/testsuite: Testing with the nvfortran compiler
Date: Thu, 22 Jun 2023 10:13:24 -0600 [thread overview]
Message-ID: <87h6qz1nmj.fsf@tromey.com> (raw)
In-Reply-To: <20230621093950.2172645-1-richard.bunt@linaro.org> (Richard Bunt via Gdb-patches's message of "Wed, 21 Jun 2023 10:39:50 +0100")
>>>>> "Richard" == Richard Bunt via Gdb-patches <gdb-patches@sourceware.org> writes:
Richard> Currently, the Fortran test suite does not run with NVIDIA's Fortran
Richard> compiler (nvfortran).
Thank you for the patch.
Richard> + } elseif {[test_compiler_info {nvfortran-*} f90]} {
Richard> + return "character*1"
I suspect this proc is returning a regular expression and so you
probably want
return "character\\*1"
There's an example of this later in the proc.
Tom
prev parent reply other threads:[~2023-06-22 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 9:39 Richard Bunt
2023-06-22 16:13 ` 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=87h6qz1nmj.fsf@tromey.com \
--to=tom@tromey.com \
--cc=agontarek@nvidia.com \
--cc=gdb-patches@sourceware.org \
--cc=richard.bunt@linaro.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).