[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED URL|

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-13 Thread rcopley at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #9 from R Copley --- For information, this has already been entered on the mingw-w64 issue tracker (months ago) (see http://sourceforge.net/p/mingw-w64/bugs/459/).

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread rcopley at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #8 from R Copley --- Thanks. I've emailed the mingw-w64 list at http://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public. (You expressed it better but I hadn't seen your last comment.)

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #7 from Jonathan Wakely --- The difference will probably be that when including libstdc++'s this happens before mingw's is included: // Make sure that POSIX printf/scanf functions are activated. As // libstdc++ depends on POSIX-de

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread rcopley at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #6 from R Copley --- Created attachment 36490 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36490&action=edit hexfloat-bug-2b.ii (see Comment 4)

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread rcopley at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #5 from R Copley --- Created attachment 36489 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36489&action=edit hexfloat-bug-2a.ii (see Comment 4)

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread rcopley at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #4 from R Copley --- That's what I understood to be the case. Nevertheless, with the toolchain I am using (see above for version; same command-line etc.), I get the results below. Both testcases below give the correct results with g

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #3 from Jonathan Wakely --- Libstdc++ has no implementation of printf, so ::printf and std::printf are exactly the same function, with std::printf defined as: namespace std { using ::printf; }

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread rcopley at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #2 from R Copley --- Thanks Jonathan. It's clear enough from what I wrote that: (1) The same kind of incorrect output is produced by (a) including and using std::printf, and (b) using iostreams and std::hexfloat; (2) The correct ou

[Bug libstdc++/67932] Incorrect conversion to hexfloat

2015-10-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67932 --- Comment #1 from Jonathan Wakely --- Your preprocessed source doesn't use std::hexfloat, so any problem comes from std::printf, which is part of your C library not part of GCC.