On 10/7/22 17:47, LIU Hao wrote:
While mingw-w64 might have been deemed to enable projects, which typically build with the Microsoft compiler and linker, to build with the GNU compiler and linker with little modification, sometimes I do think we have payed too much in mimicking some non-standard, weird, or even broken behaviors [1] [2]. If, for some necessary reasons, we can't fix them, it might be possible to build up a new series of APIs according to the C, POSIX, and Itanium ABI [3] standards.
Is there anything that mcfgthread achieves that can't be fixed in GCC's win32 model? This sounds to me like that GCC is the right place to fix things, possibly by merging parts of mcfgthread into GCC itself. I really don't like the idea of adding another threading model instead of fixing the existing one. It adds more fragmentation, more maintenance and more user confusion. I think it's better to fix the root of threading support problems instead.
(As a side note, the way winpthreads is hooked into GCC also does not seem right to me. It would be fine as a stand-alone compatibility library, but hooking it into GCC is just a hack: it replaces win32 threading model instead of fixing root of the problem).
Thanks, Jacek _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
