rfc:tls
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| rfc:tls [2008/08/26 14:23] – . lbarnaud | rfc:tls [2008/08/26 14:25] – . lbarnaud | ||
|---|---|---|---|
| Line 107: | Line 107: | ||
| Linux, Solaris, FreeBSD, Windows. | Linux, Solaris, FreeBSD, Windows. | ||
| - | Linux, Solaris and FreeBSD implementations allocate a fixed amount of surplus memory especially to allow dynamically loaded libraries to use the static model. Linux allocates 1664 bytes, FreeBSD 64 and Solaris 512. This amount of memory is always allocated in addition of the memory allocated for TLS before program startup, and is always available (this memory can be used only by dlopen()ed modules using static TLS). These behaviors are undocumented. This has been tested with a test program and verified by reading the relevant code on Linux and FreeBSD. | + | Linux, Solaris and FreeBSD implementations allocate a fixed amount of surplus memory especially to allow dynamically loaded libraries to use the static model. Linux allocates 1664 bytes, FreeBSD 64 and Solaris 512. This amount of memory is always allocated in addition of the memory allocated for TLS before program startup, and is always available (this memory can be used only by dlopen()ed modules using static TLS). These behaviors are undocumented |
| On GCC this model can be selected by using -ftls-model=initial-exec. On SunStudio: -xthreadvar=no%dynamic. For both, this model is the default one when building non-PIC code. | On GCC this model can be selected by using -ftls-model=initial-exec. On SunStudio: -xthreadvar=no%dynamic. For both, this model is the default one when building non-PIC code. | ||
rfc/tls.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1