build: use initial-exec TLS when building seastar as shared library #2255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
quote from
https://patchwork.ozlabs.org/project/glibc/patch/[email protected]/
so instead of allocating TLS variables using malloc, let's allocate them using initial-exec TLS model. another approach is to single out the static TLS variables in the code path of malloc/free and apply
__attribute__ ((tls_model("initial-exec")))
to them, and optionally only do this when we are building shared library.but this could be overkill as
see also
https://patchwork.ozlabs.org/project/glibc/patch/[email protected]/ and
https://sourceware.org/bugzilla/show_bug.cgi?id=19924
Fixes #2247
Signed-off-by: Kefu Chai [email protected]