From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
Tom de Vries <tdevries@suse.de>,
gcc@gcc.gnu.org
Subject: Re: DejaGnu: flags via 'RUNTESTFLAGS' overriding those specified in test cases
Date: Wed, 28 Sep 2022 10:39:59 -0500 [thread overview]
Message-ID: <20220928153959.GT25951@gate.crashing.org> (raw)
In-Reply-To: <CAH6eHdRUFA75ubWSCsG-Z5CM5WCEVhyweXc2WziB84qQ5hBtOg@mail.gmail.com>
On Wed, Sep 28, 2022 at 03:12:23PM +0100, Jonathan Wakely wrote:
> Which version of Dejagnu are you using? There was a fix in 6.1 or 6.2
> to change the order that the RUNTESTFLAGS and dg-options get added to
> the command line.
>
> It's a pain to make the testsuite work consistently for both old and
> new versions. I would be very happy if we just said you need a modern
> version of Dejagnu, and relied on the semantics in the newer versions.
Unfortunately there quite often are bugs in newer versions of DejaGnu
as well, making it impossible to require very new versions of it.
Segher
next prev parent reply other threads:[~2022-09-28 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-104364-4@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-104364-4-ILKfZXTaRC@http.gcc.gnu.org/bugzilla/>
2022-02-04 7:21 ` nvptx multilib setup (was: [Bug target/104364] [12 Regression] OpenMP/nvptx regressions after "[nvptx] Add some support for .local atomics") Thomas Schwinge
2022-02-04 12:09 ` Tom de Vries
2022-05-13 14:20 ` nvptx multilib setup Thomas Schwinge
2022-09-28 13:50 ` DejaGnu: flags via 'RUNTESTFLAGS' overriding those specified in test cases Thomas Schwinge
2022-09-28 14:12 ` Jonathan Wakely
2022-09-28 15:39 ` Segher Boessenkool [this message]
2022-09-29 8:18 ` Thomas Schwinge
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=20220928153959.GT25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=tdevries@suse.de \
--cc=thomas@codesourcery.com \
/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).