http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40278
Manuel López-Ibáñez manu at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
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
--- Comment #9 from paolo dot carlini at oracle dot com 2010-02-18 10:00
---
Dave, what do you recommend about this issue? Does it affect cygwin too?
--
paolo dot carlini at oracle dot com changed:
What|Removed |Added
--- Comment #10 from paolo dot carlini at oracle dot com 2010-02-18 10:12
---
In short, I see two conceptually separate issues: 1- We run the configure tests
for those functions in GNU mode, thus if on a target an header doesn't declare
some functions in ISO strict mode, the user
--- 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
--- Comment #6 from dannysmith at users dot sourceforge dot net 2009-05-28
08:26 ---
(In reply to comment #4)
Because __STRICT_ANSI__ means strict to the standard so -std=c++0x enables
__STRICT_ANSI__. But the mingw headers don't know about C++0x standard so it
does not know those
--- Comment #1 from loaden at gmail dot com 2009-05-28 00:28 ---
if use -std=c++0x, will error:
d:\ycdeng\qpdev\bin\..\lib\gcc\mingw32\4.4.1\include\c++\cwchar|159|error:
'::swprintf' has not been declared|
d:\ycdeng\qpdev\bin\..\lib\gcc\mingw32\4.4.1\include\c++\cwchar|166|error:
--- Comment #2 from pinskia at gcc dot gnu dot org 2009-05-28 00:31 ---
This sounds like a bug in mingw's stdio.h and not GCC.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40278
--- Comment #3 from loaden at gmail dot com 2009-05-28 00:48 ---
(In reply to comment #2)
This sounds like a bug in mingw's stdio.h and not GCC.
But why -std=gnu++0x is OK?
Only -std=c++0x error?
So, I think: this is not MinGW's bug, it's GCC.
--
--- Comment #4 from pinskia at gcc dot gnu dot org 2009-05-28 00:59 ---
Because __STRICT_ANSI__ means strict to the standard so -std=c++0x enables
__STRICT_ANSI__. But the mingw headers don't know about C++0x standard so it
does not know those functions should be enabled.
--
--- Comment #5 from loaden at gmail dot com 2009-05-28 04:01 ---
(In reply to comment #4)
Because __STRICT_ANSI__ means strict to the standard so -std=c++0x enables
__STRICT_ANSI__. But the mingw headers don't know about C++0x standard so it
does not know those functions should be
11 matches
Mail list logo
