public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Skip intrinsics test if arm
Date: Tue, 17 Jan 2023 17:07:08 +0000	[thread overview]
Message-ID: <4a2579d2-9740-7f2e-d249-c9f81a0f0645@foss.arm.com> (raw)
In-Reply-To: <880cd0da-dcf8-4b18-a7a2-0d21627f344c@foss.st.com>



On 15/01/2023 17:06, Torbjorn SVENSSON via Gcc-patches wrote:
> 
> 
> On 2023-01-12 16:03, Richard Earnshaw wrote:
>>
>>
>> On 19/09/2022 17:16, Torbjörn SVENSSON via Gcc-patches wrote:
>>> In the test case, it's clearly written that intrinsics is not
>>> implemented on arm*. A simple xfail does not help since there are
>>> link error and that would cause an UNRESOLVED testcase rather than
>>> XFAIL.
>>> By chaning to dg-skip-if, the entire test case is omitted.
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>>     * gcc.target/aarch64/advsimd-intrinsics/vld1x2.c: Replace
>>>     dg-xfail-if with gd-skip-if.
>>
>> Sorry for the delay reviewing this, I missed it at the time.
>>
>> My problem with your suggested solution is that if these intrinsics 
>> are ever added this test will not automatically pick this up as it 
>> will have been disabled.  I presume from the comment (and the body of 
>> the test that contains an #ifdef for aarch64) that this is expected to 
>> be a temporary issue rather than something permanent.
>>
>> So IMO I think it is correct to leave this as unresolved because the 
>> test cannot be built due to an issue with the compiler.
> 
> This patch has already been merged after Kyrill reviewed it back in 
> September.
> 
> Without this change, the log would be filled with warnings about missing 
> types. Maybe we could add some check that will enable the test only if 
> the types are known?
> Would that mitigate your concern?
> 
> Attached is the log from vld1x2.c on Cortex-A7 with -mfloat-abi=hard 
> -mfpu=neon.
> 
> When I look at the result of a run, I only look at the test cases that 
> are either FAIL (obviously), XPASS and UNRESOLVED. All other test cases 
> are in a "good" state from what I can tell. If there are a lot of test 
> cases in the UNRESOLVED state, that are not yet implemented year after 
> year, it makes it harder to identify those test cases that are of 
> interest. Right or wrong, that's why I suggested to remove it for the 
> list of test cases that should be working.
> 
> Let me know what you think.

Ah, OK.  Somehow I'd misplaced v2 of the patch, which is the version 
that got approved.

R.

> 
> Kind regards,
> Torbjörn
> 
>>
>> R.
>>
>>>
>>> Co-Authored-By: Yvan ROUX  <yvan.roux@foss.st.com>
>>> Signed-off-by: Torbjörn SVENSSON  <torbjorn.svensson@foss.st.com>
>>> ---
>>>   gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x2.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git 
>>> a/gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x2.c 
>>> b/gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x2.c
>>> index 92a139bc523..f933102be47 100644
>>> --- a/gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x2.c
>>> +++ b/gcc/testsuite/gcc.target/aarch64/advsimd-intrinsics/vld1x2.c
>>> @@ -1,6 +1,6 @@
>>>   /* We haven't implemented these intrinsics for arm yet.  */
>>> -/* { dg-xfail-if "" { arm*-*-* } } */
>>>   /* { dg-do run } */
>>> +/* { dg-skip-if "unsupported" { arm*-*-* } } */
>>>   /* { dg-options "-O3" } */
>>>   #include <arm_neon.h>

  reply	other threads:[~2023-01-17 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 16:16 Torbjörn SVENSSON
2023-01-12 15:03 ` Richard Earnshaw
2023-01-15 17:06   ` Torbjorn SVENSSON
2023-01-17 17:07     ` Richard Earnshaw [this message]
2022-09-27 14:40 Torbjörn SVENSSON
2022-09-28  8:51 ` Kyrylo Tkachov

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=4a2579d2-9740-7f2e-d249-c9f81a0f0645@foss.arm.com \
    --to=richard.earnshaw@foss.arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=torbjorn.svensson@foss.st.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).