gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr56541.c: Add vect_floatint_cvt.
OK. I'd tend to use XFAIL for a compiler bug that we haven't fixed. In
this case the target doesn't support what the test is trying to do. So
skipping the test in one manner or another seems better.
Just real
On 5/5/2021 8:31 AM, Robin Dapp via Gcc-patches wrote:
Hi,
pr56541.c implicitly converts a float vector to an int (bool) vector:
rMin = (rMax>0) ? rMin : rBig;
It fails on some s390 targets because the do not support converting
from vector float to int. Is adding a vect_floatint_cvt as in
Hi,
pr56541.c implicitly converts a float vector to an int (bool) vector:
rMin = (rMax>0) ? rMin : rBig;
It fails on some s390 targets because the do not support converting from
vector float to int. Is adding a vect_floatint_cvt as in the attached
patch the OK thing to do?
Or better an xf
