[PATCH] D19483: docs: Update SafeStack docs with separate-stack-seg feature and various USP storage modes

[Peter Collingbourne via cfe-commits]

pcc added a comment.

> This makes sense for the example I gave. However, there are also more complicated situations. Sometimes it is necessary to specify different options for different files that are compiled for the same OS. For example, early during the initialization of a dynamic linker or C library, a single-threaded mode of USP storage needs to be supported. TLS is not available at that time. How should requirements like that be conveyed to the compiler?


In cases like this, we should introduce a new `-m` flag in the Clang driver and plumb that through to the SafeStack pass using a target-specific function attribute.


http://reviews.llvm.org/D19483