Hi Joseph,
On 2022-09-23 00:42, Joseph Myers wrote:
On Thu, 22 Sep 2022, Torbjörn SVENSSON via Gcc-patches wrote:
This patch stops reporting fails for Arm targets with single
precision floating point unit for types wider than 32 bits (the width
of float on arm-none-eabi).
As reported in PR102017, fenv is reported as supported in recent
versions of newlib. At the same time, for some Arm targets, the
implementation in libgcc does not support exceptions and thus, the
test fails with a call to abort().
It's definitely wrong to have this sort of Arm-specific conditional in
architecture-independent tests. Tests requiring floating-point exceptions
support should have an appropriate dg-require-effective-target; if that
dg-require-effective-target wrongly passes in certain configurations, fix
it (or e.g. add a new check_effective_target_fenv_exceptions_double to
verify that exceptions work for double, as opposed to the present
check_effective_target_fenv_exceptions which checks whether exceptions
work for float, and then adjust tests requiring exceptions for double to
use the new effective-target).
Okay, thanks for your review.
I will split this test case into 3 files as for SP FPU, we would like to
verify that the exception handling for the float part work, but at the
same time we know that exception handling for double and long double
should not work.
Do you think it's preferable to have the double and long double should
be reported as UNSUPPORRTED, or as XFAIL for the SP FPU case?
