[Bug libstdc++/40278] -std=c++0x is error, but -std=gnu++0x is OK!

davek at gcc dot gnu dot org gcc-bugzilla@gcc.gnu.org
Thu Feb 18 12:54:00 GMT 2010



------- Comment #11 from davek at gcc dot gnu dot org  2010-02-18 12:54 -------
(In reply to comment #9)
> Dave, what do you recommend about this issue? Does it affect cygwin too?
> 

This particular problem doesn't occur on cygwin, but we've had similar issues
in the past with pre-c99 headers on cygwin (arising from newlib), although it
was easier there, since we did actually have the functionality available, so
just had to change the headers to make sure it was declared in __STRICT_ANSI__
mode.

I don't know how the MinGW guys would best like to go about tackling this, but
I'd certainly not suggest changing the configury for /all/ hosts.  Adding a
host-specific CFLAGs entry during the configure tests would be one way of
handling it at the compiler end.  Adding the required support in the mingw
library will be the ultimate way of handling it.  A third option would be for
mingw to alias their current _(v)swprintf implementations to the required names
as a stop-gap measure, on the grounds that since the resulting
compiler/toolchain is going to be not fully conformant anyway until the
functions are added, a slightly sub-spec implementation is preferable to an
entirely missing one.

Danny, it's your call.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40278



More information about the Gcc-bugs mailing list