W dniu 27.10.2018 o 13:46, Vincent Torri pisze: > On Fri, Oct 26, 2018 at 11:58 PM Mateusz <mateu...@poczta.onet.pl> wrote: >> >> W dniu 26.10.2018 o 22:35, Tom Ritter pisze: >>> This is not really a MinGW problem, but MinGW does diverge from other >>> compilers and it caused Firefox to crash. >>> >>> MinGW defines a lot of I64[foo] format specifiers in inttypes.h. >>> clang and clang-cl don't use I64[foo] they use ll[foo]. (I64[foo] is >>> valid according to Microsoft. MinGW mentions "MS runtime does not yet >>> understand C9x standard "ll"" but at some point they started >>> supporting ll[foo]. And as I mentioned, that's what clang[-cl] uses. >>> >>> Mozilla has our own implementation of printf that does the format >>> specifier parsing. We don't support I64[foo]. So using it caused data >>> corruption and general bad behavior. Switching to ll[foo] fixed it. >>> >>> I have a patch here: >>> https://hg.mozilla.org/try/raw-file/eaae7782a1dd/build/build-clang/mingw-int.patch >> >> You can try to define >> __USE_MINGW_ANSI_STDIO >> instead of patching mingw-w64 > > i've mesure a significant performance loss when using printf > functions with __USE_MINGW_ANSI_STDIO cmopared to the ones in > msvcrt.dll > > is it normal ? > > Vincent Torri
Yes, it is normal. We could try to speed up mingw_printf -- if you have some examples when the speed loss is significat please share (it was recently speed up for some cases in mingw_wprintf family -- wide char version). Regards, Mateusz _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
