diff options
| author | Christophe Lyon <christophe.lyon@linaro.org> | 2023-05-23 14:30:53 +0000 |
|---|---|---|
| committer | Christophe Lyon <christophe.lyon@linaro.org> | 2023-05-30 15:47:32 +0000 |
| commit | d12d2aa4fccc76a9a08c8120c5e37d9cab8683e8 (patch) | |
| tree | 4f63149139c65628b809371ea7c674abbf830671 /gcc/rtl.h | |
| parent | 45466eecf5ef669164c0922e5be8fd288b144886 (diff) | |
| download | gcc-d12d2aa4fccc76a9a08c8120c5e37d9cab8683e8.zip gcc-d12d2aa4fccc76a9a08c8120c5e37d9cab8683e8.tar.gz gcc-d12d2aa4fccc76a9a08c8120c5e37d9cab8683e8.tar.bz2 | |
testsuite: make mve_intrinsic_type_overloads-int.c libc-agnostic
Glibc defines int32_t as 'int' while newlib defines it as 'long int'.
Although these correspond to the same size, g++ complains when using the
'wrong' version:
invalid conversion from 'long int*' to 'int32_t*' {aka 'int*'} [-fpermissive]
or
invalid conversion from 'int*' to 'int32_t*' {aka 'long int*'} [-fpermissive]
when calling vst1q(int32*, int32x4_t) with a first parameter of type
'long int *' (resp. 'int *')
To make this test pass with any type of toolchain, this patch defines
'word_type' according to which libc is in use.
2023-05-23 Christophe Lyon <christophe.lyon@linaro.org>
gcc/testsuite/
* gcc.target/arm/mve/intrinsics/mve_intrinsic_type_overloads-int.c:
Support both definitions of int32_t.
Diffstat (limited to 'gcc/rtl.h')
0 files changed, 0 insertions, 0 deletions