On 26/07/2024 08:15, Kyrylo Tkachov wrote:
> Hi Claudio,
> 
>> On 25 Jul 2024, at 16:25, Claudio Bantaloukas <claudio.bantalou...@arm.com> 
>> wrote:
>>
>> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
>> index e0a641213ae..f293d49c61a 100644
>> --- a/gcc/doc/invoke.texi
>> +++ b/gcc/doc/invoke.texi
>> @@ -21843,6 +21843,8 @@ Enable support for Armv9.4-a Guarded Control Stack 
>> extension.
>> Enable support for Armv8.9-a/9.4-a translation hardening extension.
>> @item rcpc3
>> Enable the RCpc3 (Release Consistency) extension.
>> +@item fp8
>> +Enable the fp8 (8-bit floating point) extension.
>>
> 
> This is ok now but...
> 
> 
>> @end table
>>
>> diff --git a/gcc/testsuite/gcc.target/aarch64/acle/fp8.c 
>> b/gcc/testsuite/gcc.target/aarch64/acle/fp8.c
>> new file mode 100644
>> index 00000000000..4113758aa25
>> --- /dev/null
>> +++ b/gcc/testsuite/gcc.target/aarch64/acle/fp8.c
>> @@ -0,0 +1,21 @@
>> +/* Test the fp8 ACLE intrinsics family.  */
>> +/* { dg-do compile } */
>> +/* { dg-options "-O1 -march=armv8-a" } */
>> +/* { dg-final { check-function-bodies "**" "" "" } } */
> 
> No need for check-function-bodies here.
>

OK, will remove!

>> +
>> +#include <arm_acle.h>
>> +
>> +#ifdef __ARM_FEATURE_FP8
>> +#error "__ARM_FEATURE_FP8 feature macro defined."
>> +#endif
>> +
>> +#pragma GCC push_options
>> +#pragma GCC target("arch=armv9.4-a+fp8")
>> +
>> +/* We do not define __ARM_FEATURE_FP8 until all
>> +   relevant features have been added. */
>> +#ifdef __ARM_FEATURE_FP8
>> +#error "__ARM_FEATURE_FP8 feature macro defined."
>> +#endif
>> +
>> +#pragma GCC pop_options
> 
> … We don’t want to have failing tests in the suite. I’d recommend removing 
> this test from this patch and only adding it once the macro is defined. Or 
> otherwise you’d need to XFAIL it for now.

Actually, this will not fail. The condition is the same as the one above 
on purpose to show that we do not define __ARM_FEATURE_FP8, even if +fp8 
is passed :)
The patch to enable the define will explicitly reverse this check.

> Ok with either of those options (I prefer removing it from this patch).
> Thanks,
> Kyrill
> 

Reply via email to