From: Peter Bergner <bergner@linux.ibm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>,
Michael Meissner <meissner@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH, V2] PR target/112886, Add %S<n> to print_operand for vector pair support.
Date: Tue, 23 Jan 2024 21:11:41 -0600 [thread overview]
Message-ID: <0aef29c9-03d1-4f0c-8d7b-bf40683d57d6@linux.ibm.com> (raw)
In-Reply-To: <26fef06f-2875-d9e9-946c-1a549da5aa12@linux.ibm.com>
On 1/23/24 8:30 PM, Kewen.Lin wrote:
>> - output_operand_lossage ("invalid %%x value");
>> + output_operand_lossage ("invalid %%%c value", (code == 'S' ? 'S' : 'x'));
>
> Nit: Seems simpler with
>
> output_operand_lossage ("invalid %%%c value", (char) code);
Agreed, good catch.
>> diff --git a/gcc/testsuite/gcc.target/powerpc/pr112886.c b/gcc/testsuite/gcc.target/powerpc/pr112886.c
>> new file mode 100644
>> index 00000000000..4e59dcda6ea
>> --- /dev/null
>> +++ b/gcc/testsuite/gcc.target/powerpc/pr112886.c
>> @@ -0,0 +1,29 @@
>> +/* { dg-do compile } */
>> +/* { dg-require-effective-target power10_ok } */
>
> I think this needs one more:
>
> /* { dg-require-effective-target powerpc_vsx_ok } */
I agree with this...
>> +/* { dg-options "-mdejagnu-cpu=power10 -O2" } */
>
> ... and
>
> /* { dg-options "-mdejagnu-cpu=power10 -O2 -mvsx" } */
>
> , otherwise with explicit -mno-vsx, this test case would fail.
But not with this. The -mdejagnu-cpu=power10 option already enables -mvsx.
If the user explcitly forces -mno-vsx via RUNTESTFLAGS, then let them.
The options set in RUNTESTFLAGS come after the options in the dg-options
line, so even adding -mvsx like the above won't help the test case PASS
if we didn't have the powerpc_vsx_ok test. In other words, the -mvsx option
doesn't help with anything.
All we need is the new powerpc_vsx_ok check and that will guard against the FAIL
in the case the user forces -mno-vsx. In that case, we'll just get an UNSUPPORTED
and that is fine.
Peter
next prev parent reply other threads:[~2024-01-24 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 17:29 Michael Meissner
2024-01-19 18:51 ` Ping " Michael Meissner
2024-01-19 22:04 ` Peter Bergner
2024-01-24 2:30 ` Kewen.Lin
2024-01-24 3:11 ` Peter Bergner [this message]
2024-01-24 6:04 ` Kewen.Lin
2024-01-24 15:51 ` Peter Bergner
2024-01-25 2:15 ` 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=0aef29c9-03d1-4f0c-8d7b-bf40683d57d6@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=meissner@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).