在 2020/10/29 上午4:31, Martin Storsjö 写道: > > So with that in mind, winpthread _could_ flip the order it runs the > destructors, and it would work > with the libsupc++ implementation of __cxa_thread_atexit. Then winpthreads > would run dtors in a > different order than both glibc and darwin's, but it would run in the right > order for this usecase. > A little bit brittle maybe though? >
As far as I can tell it is only required by the c++ standard that thread_local objects are destroyed in the reverse order that they have been constructed and prior to any static destructor, and with Jeremy's patch it is guaranteed I think. The others may execute in arbitrary order. -- Best regards, LH_Mouse
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
