procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

libstdc++: Fix up 117406.cc test [PR117406]

Browse source 
Christophe mentioned in bugzilla that the test FAILs on aarch64,
I'm not including <climits> and use INT_MAX.
Apparently during my testing I got it because the test preinclude
-include bits/stdc++.h
and that includes <climits>, dunno why that didn't happen on aarch64.
In any case, either I can add #include <climits>, or because the
test already has #include <limits> I've changed uses of INT_MAX
with std::numeric_limits<int>::max(), that should be the same thing.
But if you prefer
 #include <climits>
I can surely add that instead.

2024-11-04  Jakub Jelinek  <jakub@redhat.com>

	PR libstdc++/117406
	* testsuite/26_numerics/headers/cmath/117406.cc: Use
	std::numeric_limits<int>::max() instead of INT_MAX.
This commit is contained in:
Jakub Jelinek 2024-11-04 12:29:01 +01:00 • committed by Jakub Jelinek
parent 2e6d9e9f4a
commit afcbf4dd27
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
libstdc++-v3/testsuite/26_numerics/headers/cmath/117406.cc
View file

@ -31,9 +31,9 @@ test ()
int t0 = std::ilogb(T(4.0));
VERIFY( t0 == 2 );
int t1 = std::ilogb(lim::infinity());
VERIFY( t1 == INT_MAX );
VERIFY( t1 == std::numeric_limits<int>::max() );
int t2 = std::ilogb(-lim::infinity());
VERIFY( t2 == INT_MAX );
VERIFY( t2 == std::numeric_limits<int>::max() );
}
int