diff options
| author | John Szakmeister <john@szakmeister.net> | 2016-11-23 20:32:35 (GMT) |
|---|---|---|
| committer | Jason Evans <jasone@canonware.com> | 2016-11-29 01:44:29 (GMT) |
| commit | a05d4da4d861c054260431ba113be42040173271 (patch) | |
| tree | 59bd97dd756c42a66e63cb9d18fdee7cd1d11212 /src/jemalloc_cpp.cpp | |
| parent | e98a620c59ac20b13e2de796164cc67f050ed2bf (diff) | |
| download | jemalloc-a05d4da4d861c054260431ba113be42040173271.zip jemalloc-a05d4da4d861c054260431ba113be42040173271.tar.gz jemalloc-a05d4da4d861c054260431ba113be42040173271.tar.bz2 | |
Implement a more reliable detection scheme for os_unfair_lock.
The core issue here is the weak linking of the symbol, and in certain
environments--for instance, using the latest Xcode (8.1) with the latest
SDK (10.12)--os_unfair_lock may resolve even though you're compiling on
a host that doesn't support it (10.11).
We can use the availability macros to circumvent this problem, and
detect that we're not compiling for a target that is going to support
them and error out at compile time. The other alternative is to do a
runtime check, but that presents issues for cross-compiling.
Diffstat (limited to 'src/jemalloc_cpp.cpp')
0 files changed, 0 insertions, 0 deletions