diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2022-11-24 10:37:50 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2022-11-24 10:37:50 +0100 |
| commit | d1389be011f0fac422e98e795c55156052c4d960 (patch) | |
| tree | a0cc609a4a03c3104d9f61dff1a0f253c57ad34d /gcc | |
| parent | add0f941be18cdf962a0f300019acacbf2325d41 (diff) | |
| download | gcc-d1389be011f0fac422e98e795c55156052c4d960.zip gcc-d1389be011f0fac422e98e795c55156052c4d960.tar.gz gcc-d1389be011f0fac422e98e795c55156052c4d960.tar.bz2 | |
libstdc++: Workaround buggy printf on Solaris in to_chars/float128_c++23.cc test [PR107815]
As mentioned in the PR, Solaris apparently can handle right
printf ("%.0Lf\n", 1e+202L * __DBL_MAX__);
which prints 511 chars long number, but can't handle
printf ("%.0Lf\n", 1e+203L * __DBL_MAX__);
nor
printf ("%.0Lf\n", __LDBL_MAX__);
properly, instead of printing 512 chars long number for the former and
4933 chars long number for the second, it handles them as
if user asked for "%.0Le\n" in those cases.
The following patch disables the single problematic value that fails
in the test, and also fixes commented out debugging printouts.
2022-11-24 Jakub Jelinek <jakub@redhat.com>
PR libstdc++/107815
* testsuite/20_util/to_chars/float128_c++23.cc (test): Disable
__FLT128_MAX__ test on Solaris. Fix up commented out debugging
printouts.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions