[Patch / Request For Testers] libstdc++/34032

[Paolo Carlini]

Hi,

as discussed in the audit trail, the issue here is that on some targets
(cygwin / newlib for sure), an undefined __STRICT_ANSI__ enables some
extensions which can appear to the autoconf tests as genuine C99
facilities: first, the risk is serious (e.g., certainly there are around
unreliable non-conforming snprintf); second, those facilities all of a
sudden disappear from the underlying C headers when the user passes
-std=c++98 (or -std=c++0x) instead of the default (ie, -std=gnu++98) and
the compilation breaks. Seems safe to me just running the sensitive
autoconf test with -std=c++98 and I also checked that nothing breaks on
gnu-linux (i.e., viceversa, __STRICT_ANSI__ doesn't disable any real C99
facility).

It would be nice if Eric could double check and possibly other test on,
eg, darwin, which normally enables as many C99 facilities as gnu-linux.

Paolo.

/////////////////
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_34032_draft
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20071109/024cbec2/attachment.ksh>