Paul Eggert wrote:
On 04/19/2017 05:13 AM, Gisle Vanem wrote:
With "%.3a %d", I do get the expected "0x1.922p+1 33".
So are these tests somewhat gcc-centric or what?
Yes. It looks to me like MSVC-2015 is right and glibc is wrong, at least in the
sense of acting like standard printf.
It seems strange there should be a difference in output since
MSVC internal *printf() seems not involved. Does this perhaps has
something to do with 'BEGIN_LONG_DOUBLE_ROUNDING()' used in
printf-frexp.c?
This macro is effective for gcc only using inline assembly.
It could be done using '_controlfp()' (or '_controlfp_s()')
for MSVC too AFAICS.
--
--gv
