diff options
author | Jonathan Wakely <jwakely@redhat.com> | 2021-10-11 13:28:32 +0100 |
---|---|---|
committer | Jonathan Wakely <jwakely@redhat.com> | 2021-10-11 20:34:17 +0100 |
commit | 45ba5426c129993704a73e6ace4016eaa950d7ee (patch) | |
tree | dc32fb822cb6e44d385eac47ab7583671bb03571 /gcc | |
parent | 6b6788f8c2748060d922cc22173ff7f8500917e9 (diff) | |
download | gcc-45ba5426c129993704a73e6ace4016eaa950d7ee.zip gcc-45ba5426c129993704a73e6ace4016eaa950d7ee.tar.gz gcc-45ba5426c129993704a73e6ace4016eaa950d7ee.tar.bz2 |
libstdc++: Fix std::numeric_limits::lowest() test for strict modes
This test uses std::is_integral to decide whether we are testing an
integral or floating-point type. But that fails for __int128 because
is_integral<__int128> is false in strict modes. By using
numeric_limits::is_integer instead we get the right answer for all types
that have a numeric_limits specialization.
We can also simplify the test by removing the unnecessary tag
dispatching.
libstdc++-v3/ChangeLog:
* testsuite/18_support/numeric_limits/lowest.cc: Use
numeric_limits<T>::is_integer instead of is_integral<T>::value.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions