http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52015
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-27
Ever Confirmed|0 |1
--- Comment #6 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-02-27 18:14:55
UTC ---
(In reply to comment #4)
> I'm pretty sure that Kai / the target maintainers did some work to actually
> make available the underlying libc function on those systems, thus I can
> imagine that just tweaking a bit the configury could do the trick, and in that
> case a fix could go in for 4.7.1. Well, if Kai can tell us that the tweak is
> *really* trivial and totally restricted to MinGW, maybe even 4.7.0,
> conditional
> to release managers approval, of course.
Well, I thought about fixing this issue for 4.7 using mingw-w64's runtime. It
should be doable, as mingw-w64 provides also wide printf/scanf (and ansi scanf)
functions with glibc behavior. The dfp aren't supported there right now, but
this is something we will come up in future. Also for 4.7 libstdc++ uses for
mingw-w64 configure variant by default posix-compatible printf/scanf API.
I didn't found time to dive in more detail into this issue.
