SafeStack uses thread-local storage by default in most OSes for the unsafe stack
pointer. For SafeStack to be applied to functions that may be invoked while
initializing the dynamic linker and libc, the functions can be compiled to
support a single-threaded unsafe stack pointer. This flag signals that such code
should be emitted.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I was able to setup a temporary thread control block early enough in musl libc initialization to obviate the need for an attribute like runtime_init.