Re: [Mingw-w64-public] Proposition for locking printf

2015-08-01 Thread JonY
On 8/2/2015 06:27, Mateusz wrote: We have 4 functions from printf family that output to FILE stream: printf, vprintf, fprintf, vfprintf We have also puts/fputs functions that output to FILE stream and are always directly from msvcrt.dll. puts/fputs functions are atomic with Microsoft

[Mingw-w64-public] Patch: complete implementation of intsafe.h

2015-08-01 Thread David Grayson
Hello. Attached is a patch that adds a complete implementation of intsafe.h that I generated and tested using Ruby. It would be great if someone could merge it in. The version of intsafe.h included in this patch can also be viewed here:

Re: [Mingw-w64-public] Proposition for locking printf

2015-08-01 Thread Mateusz
I'm not diff expert, but I tried git diff -- maybe now is better. Due to problem with new file I copy context of mingw_lock.c to smallest ftello.c -- surprisingly make install works and with new libmingwex.a I can compile test-stdio.c file and it is working. Could you/Kai show example of

[Mingw-w64-public] Proposition for locking printf

2015-08-01 Thread Mateusz
We have 4 functions from printf family that output to FILE stream: printf, vprintf, fprintf, vfprintf We have also puts/fputs functions that output to FILE stream and are always directly from msvcrt.dll. puts/fputs functions are atomic with Microsoft lock. If we want mingw-w64 printf