From: Tom Tromey <tom@tromey.com>
To: "Willgerodt, Felix via Gdb-patches" <gdb-patches@sourceware.org>
Subject: Re: [PUSHED] gdb/testsuite: only add -J option when compiling with gfortran
Date: Wed, 02 Jun 2021 11:12:10 -0600 [thread overview]
Message-ID: <874kegqjh1.fsf@tromey.com> (raw)
In-Reply-To: <1849faf7e8a348c79cacc7ec88f586c0@intel.com> (Felix via Gdb-patches Willgerodt's message of "Wed, 2 Jun 2021 09:45:13 +0000")
>> I have no proper fix really, as test_compiler_info relies on a c
>> program to figure out which compiler is in use :/ This is rather
>> annoying, as using F90_FOR_TARGET in RUNTESTFLAGS won't be enough.
It's fine to add a proc to test the properties of the relevant compiler.
See, e.g., rust_llvm_version in gdb/testsuite/lib/rust-support.exp.
Tom
prev parent reply other threads:[~2021-06-02 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 9:22 Andrew Burgess
2021-06-02 9:45 ` Willgerodt, Felix
2021-06-02 17:12 ` 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=874kegqjh1.fsf@tromey.com \
--to=tom@tromey.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).