On Sat, Sep 19, 2009 at 9:20 AM, Erik de Castro Lopo
mle+...@mega-nerd.com wrote:
Ozkan Sezer wrote:
- Which svn revision of mingw-w64 headers and crt did you
use in your toolchain ?
Same revision for both :
Path: .
URL: https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/trunk
On Sat, Sep 19, 2009 at 11:02 AM, Erik de Castro Lopo
mle+...@mega-nerd.com wrote:
Ozkan Sezer wrote:
Hmm, with my versions gcc-4.4.2 (svn r151768, patched but
nothing that would affect this) and mingw-w64 r1375-r1378,
I get:
x86_64-pc-mingw32-gcc -Wall -std=gnu99 test.c
test.c: In
Ozkan Sezer wrote:
You need it with both. (Although, if your w32 toolchain is
a mingw.org toolchain and not ours, they may have automatically
defined __USE_MINGW_ANSI_STDIO as 1 upon seeing -std=c99. Kai,
should we do that?)
Yes, please!
Cheers,
Erik
--
On Sat, Sep 19, 2009 at 1:13 PM, Erik de Castro Lopo
mle+...@mega-nerd.com wrote:
Ozkan Sezer wrote:
You need it with both. (Although, if your w32 toolchain is
a mingw.org toolchain and not ours, they may have automatically
defined __USE_MINGW_ANSI_STDIO as 1 upon seeing -std=c99. Kai,
On Sat, Sep 19, 2009 at 1:38 PM, Kai Tietz ktiet...@googlemail.com wrote:
Ok, add it to our _mingw.h file, too. We can then simplify our logic
Will do.
in our _mingw_printf_(push/pop).h headers, too, as we know that
__USE_MINGW_ANSI_STDIO is defined in any case to zero or one, isn't
it?
If
Ozkan Sezer wrote:
OK, applied this as rev. 1395:
http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=revrevision=1395
Please test.
Real close!
I get the proper C99 behaviour if I compile with:
x86_64-w64-mingw32-gcc -Wall -std=c99 test.c -o test
but with this:
On Sun, Sep 20, 2009 at 1:08 AM, Erik de Castro Lopo
mle+...@mega-nerd.com wrote:
Ozkan Sezer wrote:
OK, applied this as rev. 1395:
http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=revrevision=1395
Please test.
Real close!
I get the proper C99 behaviour if I compile with:
