From: Peter Bergner <bergner@linux.ibm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000/test: Fix bswap64-4.c with has_arch_ppc64 [PR106680]
Date: Wed, 31 Aug 2022 09:13:51 -0500 [thread overview]
Message-ID: <4e527a22-2dd6-9fa3-b255-4f71b90b77f7@linux.ibm.com> (raw)
In-Reply-To: <69277846-f587-b79e-f741-a2942d326778@linux.ibm.com>
On 8/31/22 4:33 AM, Kewen.Lin wrote:
> @@ -1,7 +1,8 @@
> /* { dg-do compile { target { powerpc*-*-* } } } */
> /* { dg-skip-if "" { powerpc*-*-aix* } } */
> -/* { dg-options "-O2 -mpowerpc64" } */
> /* { dg-require-effective-target ilp32 } */
> +/* { dg-options "-O2 -mpowerpc64" } */
> +/* { dg-require-effective-target has_arch_ppc64 } */
With many of our recent patches moving the dg-options before any
dg-requires-effectice-target so it affects the results of the
dg-requires-effectice-target test, this looks like it's backwards
from that process. I understand why, so I think an explicit comment
here in the test case explaining why it's after in this case.
Just so in a few years when we come back to this test case, we
won't accidentally undo this change.
The other option would be to introduce -mdejagnu-32 and -mdejagnu-64
options that operate like our -mdejagnu-cpu= options and override any
-m32/-m64 option given on the command line (eg, RUNTESTFLAGS=...).
To be honest, I'm not sure how I feel about this suggestion! :-)
Maybe we'd only use it on the test cases like this one that we know
are sensitive to be overridden???
Peter
next prev parent reply other threads:[~2022-08-31 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:33 Kewen.Lin
2022-08-31 14:13 ` Peter Bergner [this message]
2022-09-01 8:57 ` Kewen.Lin
2022-09-01 14:57 ` Segher Boessenkool
2022-09-02 0:50 ` Kewen.Lin
2022-09-02 17:36 ` Segher Boessenkool
2022-09-05 2:25 ` Kewen.Lin
2022-08-31 15:24 ` Segher Boessenkool
2022-08-31 15:48 ` Peter Bergner
2022-08-31 16:05 ` Segher Boessenkool
2022-08-31 17:00 ` Peter Bergner
2022-08-31 19:28 ` Segher Boessenkool
2022-08-31 19:53 ` Peter Bergner
2022-08-31 21:07 ` Segher Boessenkool
2022-08-31 21:38 ` Peter Bergner
2022-08-31 21:49 ` Segher Boessenkool
2022-08-31 22:17 ` Peter Bergner
2022-09-01 9:05 ` Kewen.Lin
2022-09-01 15:04 ` Segher Boessenkool
2022-09-02 0:51 ` Kewen.Lin
2022-09-02 17:44 ` Segher Boessenkool
2022-09-05 2:35 ` Kewen.Lin
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=4e527a22-2dd6-9fa3-b255-4f71b90b77f7@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.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).