Ah yes, for gcc it is required. Have you looked at clang implementation? it support native TLS, it would be really nice if the implementation would be compatible.
2015-06-08 15:58 GMT+03:00 Alexandre Pereira Nunes < alexandre.nu...@gmail.com>: > Yes, but I'd need to patch GCC as well. The bureaucracies are regarding > the Free Software Foundation Copyright claims on it, they need a copyright > transfer or waiver. > > Em seg, 8 de jun de 2015 às 09:52, Yaron Keren <yaron.ke...@gmail.com> > escreveu: > >> This is a great idea. >> >> Regarding the license, isn't mingw-w64 released under a public domain or >> CC0 license? >> >> >> http://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/thread/5238f91b.7010...@tdragon.net/ >> >> >> 2015-06-08 15:41 GMT+03:00 Alexandre Pereira Nunes < >> alexandre.nu...@gmail.com>: >> >>> Hi, >>> I read in the mailing list archives that some work was done on the area >>> of implementing native TLS support and I'm interested in continuing it, in >>> case nobody is currently on it. >>> >>> My initial goal would be to have an implementation that would be both >>> thread-model agnostic (i.e. be both sufficient and compatible with current >>> posix & win32 gcc thread models), leveraging the current dependency on >>> gthreads (and the consequent libpthread one in case of the posix thread >>> model). >>> >>> For that I thought about patching gcc to generate native TLS compatible >>> with win32/msvc semantics. Or, if that's too hard, at least provide a >>> better emulation (perhaps using TlsAlloc() & friends), preferably one that >>> doesn't rely on mutexes. But I don't want to go to deep without information >>> from those who attempted something like that in the past. >>> >>> I'm currently awaiting for feedback from fsf on my papers, but a small >>> amount of work (perhaps for early testing) can be early released >>> accordingly to fsf statements in the form of small patches, should that be >>> needed / convenient. >>> >>> A further goal would be to investigate this report and fix it if >>> possible (and if not fixed as a side effect of the planned ork): >>> https://sourceforge.net/p/mingw-w64/bugs/445/ >>> >>> Cheers, >>> >>> Alexandre >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Mingw-w64-public mailing list >>> Mingw-w64-public@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public >>> >>> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Mingw-w64-public mailing list >> Mingw-w64-public@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > >
------------------------------------------------------------------------------
_______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
