From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Carl Love <cel@us.ibm.com>
Cc: Peter Bergner <bergner@linux.ibm.com>,
gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] rs6000: Fix test gc.target/powerpc/rs600-fpint.c test options
Date: Mon, 15 May 2023 14:46:20 +0800 [thread overview]
Message-ID: <bff4f450-46d3-9b1c-70a9-ed7676dc8d77@linux.ibm.com> (raw)
In-Reply-To: <c7e61083e9a2a8154a18a6c4ffe22ae8751ad3f0.camel@us.ibm.com>
Hi Carl,
on 2023/4/14 03:42, Carl Love via Gcc-patches wrote:
>
> GCC maintainers:
>
> The following patch fixes the dg-options for test powerpc/rs600-
> fpint.c. The test now works correctly on Power 10. The patch has been
> tested on Power10 with no regressions.
>
> Please let me know if the patch is acceptable for mainline. Thanks.
OK for trunk with one more comment added in commit log ...
>
> Carl
>
> ---------------------------------
> rs6000: Fix test gc.target/powerpc/rs600-fpint.c test options
>
> The test compile option rs6000-*-* is outdated and no longer supported.
> The powerpc*-*-* is the defualt, so it doesn't need to be specified.
> The dg-options needs to specify an older processor to get the desired
> behavior on recent processors.
... such as: ", since gfxopt is only off for very old CPUs, we don't guard
stfiwx under it for recent processors and don't want to." Thanks for fixing!
BR,
Kewen
>
> This patch updates the test specifications so the test will run properly on
> Power10LE. Tested on Power10 LE system with no regression test failures.
>
> gcc/testsuite/:
> * gcc.target/powerpc/rs6000-fpint.c: Update dg-options, drop dg-do
> compile specifier.
> ---
> gcc/testsuite/gcc.target/powerpc/rs6000-fpint.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/gcc/testsuite/gcc.target/powerpc/rs6000-fpint.c b/gcc/testsuite/gcc.target/powerpc/rs6000-fpint.c
> index 410f780de8b..fdb0a371929 100644
> --- a/gcc/testsuite/gcc.target/powerpc/rs6000-fpint.c
> +++ b/gcc/testsuite/gcc.target/powerpc/rs6000-fpint.c
> @@ -1,5 +1,4 @@
> -/* { dg-do compile { target powerpc*-*-* rs6000-*-* } } */
> -/* { dg-options "-mno-powerpc-gfxopt" } */
> +/* { dg-options "-mno-powerpc-gfxopt -mdejagnu-cpu=power6" } */
> /* { dg-final { scan-assembler-not "stfiwx" } } */
>
> /* A basic test of the old-style (not stfiwx) fp -> int conversion. */
prev parent reply other threads:[~2023-05-15 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:42 Carl Love
2023-05-15 6:46 ` Kewen.Lin [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=bff4f450-46d3-9b1c-70a9-ed7676dc8d77@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=cel@us.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--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).