This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/40278] -std=c++0x is error, but -std=gnu++0x is OK!
- From: "ktietz at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 16 Jan 2012 09:49:14 +0000
- Subject: [Bug libstdc++/40278] -std=c++0x is error, but -std=gnu++0x is OK!
- Auto-submitted: auto-generated
- References: <bug-40278-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40278
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-01-16
CC| |ktietz at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #12 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-01-16 09:49:14 UTC ---
Hmm, this issue doesn't occure with mingw-w64 for 32-bit or 64-bit. This is
related to the fact that mingw-w64 provides also the wide-character
printf/scanf family in unix-way.
So I would suggest to close this bug here, as it is a mingw.org runtime issue.