]> git.ipfire.org Git - thirdparty/gcc.git/commit - libstdc++-v3/testsuite/18_support/numeric_limits/lowest.cc
libstdc++: Fix std::numeric_limits::lowest() test for strict modes
authorJonathan Wakely <jwakely@redhat.com>
Mon, 11 Oct 2021 12:28:32 +0000 (13:28 +0100)
committerJonathan Wakely <jwakely@redhat.com>
Mon, 11 Oct 2021 19:34:17 +0000 (20:34 +0100)
commit45ba5426c129993704a73e6ace4016eaa950d7ee
treedc32fb822cb6e44d385eac47ab7583671bb03571
parent6b6788f8c2748060d922cc22173ff7f8500917e9
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.
libstdc++-v3/testsuite/18_support/numeric_limits/lowest.cc