https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192320
--- Comment #4 from David Chisnall <thera...@freebsd.org> --- I'm still not completely sure what the correct solution for implementing this is. Clang will always lazily construct thread_local objects on first access (which means that you can't use them to track thread counts and so on, which limits their use somewhat), but the destructors will run when the thread exits. Unfortunately, the destructors might not be signal safe and so there is no *good* way of running them on library unload. A complete solution most likely involves locking the library in memory while it has outstanding thread-local objects. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
