From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, dejagnu@gnu.org, gcc-patches@gnu.org
Subject: Re: dg-options after board/cflags
Date: Mon, 28 Sep 2020 16:07:48 +0200 [thread overview]
Message-ID: <87lfgu570r.fsf@oracle.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2009261327020.3561363@eddie.linux-mips.org> (Maciej W. Rozycki's message of "Sat, 26 Sep 2020 13:33:40 +0100 (BST)")
>> Your patch dealt with board/multilib_flags, but the same problem exists
>> for board/cflags and many other flag-containing options.
>
> What's the use case for that? IIUC board flags are supposed to be ones
> that are absolutely required for executables to run with a given board,
> such as multilib selection, special linker scripts, non-standard run-time
> library paths, etc. These must not be overridden by test cases or they
> will inevitably fail.
We want to build most bpf-unknown-none test files with -mxbpf, but not
all.
I wasn't aware of the "absolutely require" nature of the board
flags... then it is clear we need to find another strategy, like
specifying it in the individual test files/dg-options.
prev parent reply other threads:[~2020-09-28 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:30 Jose E. Marchesi
2020-09-02 16:30 ` H.J. Lu
2020-09-02 16:47 ` Jose E. Marchesi
2020-09-26 12:33 ` Maciej W. Rozycki
2020-09-28 14:07 ` Jose E. Marchesi [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=87lfgu570r.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=dejagnu@gnu.org \
--cc=gcc-patches@gnu.org \
--cc=hjl.tools@gmail.com \
--cc=macro@linux-mips.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).