]> git.ipfire.org Git - thirdparty/gcc.git/commit
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>
Fri, 23 Jun 2023 16:08:17 +0000 (17:08 +0100)
commitf11b715ba891ecc936888cc5d4d6a3fab192b5f6
tree64461fc7bbecf3978e039aab06ea3ad67a661ad2
parent291df257830e4ff877c716cfe6430c03677d9606
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.

(cherry picked from commit 45ba5426c129993704a73e6ace4016eaa950d7ee)
libstdc++-v3/testsuite/18_support/numeric_limits/lowest.cc