https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110145
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #1) > Weird, the 1e126 constant shouldn't be with excess precision because it is > stored into a double field (using ctor). Yeah, I've fixed nearly all the other tests that fail with -fexcess-precision=standard but this one confused me. I don't know what's happening. > So perhaps the to_chars implementation actually relying somewhere on excess > precision not happening? Given that all the implementation is inside libstdc++.so I don't see how it can be affected by the options used to include the <charconv> header in the testcase.
