public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Saurabh Jha <saurabh.jha@arm.com>,
	Richard Sandiford via Gcc-patches <gcc-patches@gcc.gnu.org>,
	Richard Sandiford <Richard.Sandiford@arm.com>,
	Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Subject: Re: [PATCH v2] testsuite, arm: Fix testcase arm/pr112337.c to check for the options first
Date: Tue, 5 Mar 2024 15:31:52 +0000	[thread overview]
Message-ID: <f1b7e319-376b-4f23-b61a-ab69c3391f23@arm.com> (raw)
In-Reply-To: <12c0edc0-4b22-4d7e-8ad5-1db0632f7cc5@arm.com>

On 19/02/2024 10:11, Saurabh Jha wrote:
> 
> On 2/9/2024 2:57 PM, Richard Earnshaw (lists) wrote:
>> On 30/01/2024 17:07, Saurabh Jha wrote:
>>> Hey,
>>>
>>> Previously, this test was added to fix this bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337. However, it did not check the compilation options before using them, leading to errors.
>>>
>>> This patch fixes the test by first checking whether it can use the options before using them.
>>>
>>> Tested for arm-none-eabi and found no regressions. The output of check-gcc with RUNTESTFLAGS="arm.exp=*" changed like this:
>>>
>>> Before:
>>> # of expected passes          5963
>>> # of unexpected failures      64
>>>
>>> After:
>>> # of expected passes          5964
>>> # of unexpected failures      63
>>>
>>> Ok for master?
>>>
>>> Regards,
>>> Saurabh
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>>          * gcc.target/arm/pr112337.c: Check whether we can use the compilation options before using them.
>> My apologies for missing this earlier.  It didn't show up in patchwork. That's most likely because the attachment is a binary blob instead of text/plain.  That also means that the Linaro CI system hasn't seen this patch either.  Please can you fix your mailer to add plain text patch files.
>>
>> -/* { dg-options "-O2 -march=armv8.1-m.main+fp.dp+mve.fp -mfloat-abi=hard" } */
>> +/* { dg-require-effective-target arm_hard_ok } */
>> +/* { dg-require-effective-target arm_v8_1m_mve_ok } */
>> +/* { dg-options "-O2 -mfloat-abi=hard" } */
>> +/* { dg-add-options arm_v8_1m_mve } */
>>
>> This is moving in the right direction, but it adds more than necessary now: checking for, and adding -mfloat-abi=hard is not necessary any more as arm_v8_1m_mve_ok will work out what float-abi flags are needed to make the options work. (What's more, it will prevent the test from running if the base configuration of the compiler is incompatible with the hard float ABI, which is more than we need.).
>>
>> So please can you re-spin removing the hard-float check and removing that from dg-options.
>>
>> Thanks,
>> R.
> 
> Hi Richard,
> 
> Agreed with your comments. Please find the patch with the suggested changes attached.
> 
> Regards,
> 
> Saurabh
> 


Thanks, I've pushed this.  Next time, please can you put the commit message inside the patch, so that I can apply things automatically.  Eg: 

From 1c92c94074449929f40cea99a6450bcde3aec12f Mon Sep 17 00:00:00 2001
From: Saurabh Jha <saujha01@e130340.arm.com>
Date: Tue, 30 Jan 2024 15:03:36 +0000
Subject: [PATCH] Fix testcase pr112337.c to check the options [PR112337]

gcc.target/arm/pr112337.c was failing to validate that adding MVE options
was compatible with the test environment, so add the missing checks.

gcc/testsuite/ChangeLog:

	PR target/112337
	* gcc.target/arm/pr112337.c: Check for, then use the right MVE
	options.
	
---
 gcc/testsuite/gcc.target/arm/pr112337.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/arm/pr112337.c b/gcc/testsuite/gcc.target/arm/pr112337.c

...

      parent reply	other threads:[~2024-03-05 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 17:07 [PATCH] " Saurabh Jha
2024-02-09 11:35 ` Saurabh Jha
2024-02-09 14:57 ` Richard Earnshaw (lists)
2024-02-19 10:11   ` [PATCH v2] " Saurabh Jha
2024-03-05  9:56     ` Saurabh Jha
2024-03-05 15:31     ` Richard Earnshaw (lists) [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=f1b7e319-376b-4f23-b61a-ab69c3391f23@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=Kyrylo.Tkachov@arm.com \
    --cc=Richard.Sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=saurabh.jha@arm.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).