2016-05-06 22:06:29 +08:00
|
|
|
// -*- C++ -*-
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is dual licensed under the MIT and the University of Illinois Open
|
|
|
|
// Source Licenses. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#ifndef _LIBCPP_THREADING_SUPPORT
|
|
|
|
#define _LIBCPP_THREADING_SUPPORT
|
|
|
|
|
|
|
|
#include <__config>
|
2017-02-09 17:31:41 +08:00
|
|
|
#include <chrono>
|
|
|
|
#include <errno.h>
|
2016-05-06 22:06:29 +08:00
|
|
|
|
|
|
|
#ifndef _LIBCPP_HAS_NO_PRAGMA_SYSTEM_HEADER
|
|
|
|
#pragma GCC system_header
|
|
|
|
#endif
|
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#if defined(_LIBCPP_HAS_THREAD_API_EXTERNAL)
|
|
|
|
# include <__external_threading>
|
|
|
|
#elif !defined(_LIBCPP_HAS_NO_THREADS)
|
2017-01-03 10:00:31 +08:00
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#if defined(_LIBCPP_HAS_THREAD_API_PTHREAD)
|
|
|
|
# include <pthread.h>
|
|
|
|
# include <sched.h>
|
2017-01-07 11:07:45 +08:00
|
|
|
#elif defined(_LIBCPP_HAS_THREAD_API_WIN32)
|
2017-05-26 06:37:15 +08:00
|
|
|
#include <windows.h>
|
2017-01-07 11:07:45 +08:00
|
|
|
#include <process.h>
|
|
|
|
#include <fibersapi.h>
|
2017-01-03 10:00:31 +08:00
|
|
|
#endif
|
2016-05-06 22:06:29 +08:00
|
|
|
|
2017-06-01 06:07:49 +08:00
|
|
|
_LIBCPP_PUSH_MACROS
|
|
|
|
#include <__undef_macros>
|
|
|
|
|
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#if defined(_LIBCPP_HAS_THREAD_LIBRARY_EXTERNAL) || \
|
|
|
|
defined(_LIBCPP_BUILDING_THREAD_LIBRARY_EXTERNAL)
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
#define _LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_FUNC_VIS
|
|
|
|
#else
|
|
|
|
#define _LIBCPP_THREAD_ABI_VISIBILITY inline _LIBCPP_INLINE_VISIBILITY
|
|
|
|
#endif
|
2016-05-06 22:06:29 +08:00
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
#if defined(__FreeBSD__) && defined(__clang__) && __has_attribute(no_thread_safety_analysis)
|
|
|
|
#define _LIBCPP_NO_THREAD_SAFETY_ANALYSIS __attribute__((no_thread_safety_analysis))
|
|
|
|
#else
|
|
|
|
#define _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
|
|
|
#endif
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_BEGIN_NAMESPACE_STD
|
2016-05-06 22:06:29 +08:00
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#if defined(_LIBCPP_HAS_THREAD_API_PTHREAD)
|
2016-05-06 22:06:29 +08:00
|
|
|
// Mutex
|
|
|
|
typedef pthread_mutex_t __libcpp_mutex_t;
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
#define _LIBCPP_MUTEX_INITIALIZER PTHREAD_MUTEX_INITIALIZER
|
|
|
|
|
2017-01-06 01:54:45 +08:00
|
|
|
typedef pthread_mutex_t __libcpp_recursive_mutex_t;
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
// Condition Variable
|
|
|
|
typedef pthread_cond_t __libcpp_condvar_t;
|
|
|
|
#define _LIBCPP_CONDVAR_INITIALIZER PTHREAD_COND_INITIALIZER
|
|
|
|
|
2017-01-03 20:59:50 +08:00
|
|
|
// Execute once
|
|
|
|
typedef pthread_once_t __libcpp_exec_once_flag;
|
|
|
|
#define _LIBCPP_EXEC_ONCE_INITIALIZER PTHREAD_ONCE_INIT
|
|
|
|
|
|
|
|
// Thread id
|
2017-01-03 10:00:31 +08:00
|
|
|
typedef pthread_t __libcpp_thread_id;
|
|
|
|
|
|
|
|
// Thread
|
2017-01-16 20:19:54 +08:00
|
|
|
#define _LIBCPP_NULL_THREAD 0U
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
typedef pthread_t __libcpp_thread_t;
|
|
|
|
|
|
|
|
// Thrad Local Storage
|
|
|
|
typedef pthread_key_t __libcpp_tls_key;
|
2017-01-07 11:07:45 +08:00
|
|
|
|
|
|
|
#define _LIBCPP_TLS_DESTRUCTOR_CC
|
|
|
|
#else
|
|
|
|
// Mutex
|
|
|
|
typedef SRWLOCK __libcpp_mutex_t;
|
|
|
|
#define _LIBCPP_MUTEX_INITIALIZER SRWLOCK_INIT
|
|
|
|
|
|
|
|
typedef CRITICAL_SECTION __libcpp_recursive_mutex_t;
|
|
|
|
|
|
|
|
// Condition Variable
|
|
|
|
typedef CONDITION_VARIABLE __libcpp_condvar_t;
|
|
|
|
#define _LIBCPP_CONDVAR_INITIALIZER CONDITION_VARIABLE_INIT
|
|
|
|
|
|
|
|
// Execute Once
|
|
|
|
typedef INIT_ONCE __libcpp_exec_once_flag;
|
|
|
|
#define _LIBCPP_EXEC_ONCE_INITIALIZER INIT_ONCE_STATIC_INIT
|
|
|
|
|
|
|
|
// Thread ID
|
|
|
|
typedef DWORD __libcpp_thread_id;
|
|
|
|
|
|
|
|
// Thread
|
2017-01-16 20:19:54 +08:00
|
|
|
#define _LIBCPP_NULL_THREAD 0U
|
|
|
|
|
2017-01-07 11:07:45 +08:00
|
|
|
typedef HANDLE __libcpp_thread_t;
|
|
|
|
|
|
|
|
// Thread Local Storage
|
|
|
|
typedef DWORD __libcpp_tls_key;
|
|
|
|
|
|
|
|
#define _LIBCPP_TLS_DESTRUCTOR_CC WINAPI
|
2017-01-03 10:00:31 +08:00
|
|
|
#endif
|
|
|
|
|
|
|
|
// Mutex
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-06 01:54:45 +08:00
|
|
|
int __libcpp_recursive_mutex_init(__libcpp_recursive_mutex_t *__m);
|
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-06 01:54:45 +08:00
|
|
|
int __libcpp_recursive_mutex_lock(__libcpp_recursive_mutex_t *__m);
|
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-14 18:27:12 +08:00
|
|
|
bool __libcpp_recursive_mutex_trylock(__libcpp_recursive_mutex_t *__m);
|
2017-01-06 01:54:45 +08:00
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-06 01:54:45 +08:00
|
|
|
int __libcpp_recursive_mutex_unlock(__libcpp_recursive_mutex_t *__m);
|
|
|
|
|
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
int __libcpp_recursive_mutex_destroy(__libcpp_recursive_mutex_t *__m);
|
2017-01-03 10:00:31 +08:00
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_mutex_lock(__libcpp_mutex_t *__m);
|
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-14 18:27:12 +08:00
|
|
|
bool __libcpp_mutex_trylock(__libcpp_mutex_t *__m);
|
2017-01-03 10:00:31 +08:00
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_mutex_unlock(__libcpp_mutex_t *__m);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_mutex_destroy(__libcpp_mutex_t *__m);
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
|
|
|
|
// Condition variable
|
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
int __libcpp_condvar_signal(__libcpp_condvar_t* __cv);
|
2017-01-03 10:00:31 +08:00
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
int __libcpp_condvar_broadcast(__libcpp_condvar_t* __cv);
|
2017-01-03 10:00:31 +08:00
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
int __libcpp_condvar_wait(__libcpp_condvar_t* __cv, __libcpp_mutex_t* __m);
|
2017-01-03 10:00:31 +08:00
|
|
|
|
Disable thread safety analysis for some functions in __thread_support
Many thread-related libc++ test cases fail on FreeBSD, due to the
following -Werror warnings:
In file included from test/std/thread/thread.threads/thread.thread.this/sleep_until.pass.cpp:17:
In file included from include/thread:97:
In file included from include/__mutex_base:17:
include/__threading_support:222:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:221:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:231:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:242:1: error: mutex '__m' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
include/__threading_support:241:10: note: mutex acquired here
return pthread_mutex_lock(__m);
^
include/__threading_support:251:10: error: releasing mutex '__m' that was not held [-Werror,-Wthread-safety-analysis]
return pthread_mutex_unlock(__m);
^
include/__threading_support:272:10: error: calling function 'pthread_cond_wait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_wait(__cv, __m);
^
include/__threading_support:278:10: error: calling function 'pthread_cond_timedwait' requires holding mutex '__m' exclusively [-Werror,-Wthread-safety-analysis]
return pthread_cond_timedwait(__cv, __m, __ts);
^
6 errors generated.
This is because on FreeBSD, the pthread functions have lock annotations.
Since the functions in __thread_support are internal to libc++ only, add
no_thread_safety_analysis attributes to suppress these warnings.
Reviewers: mclow.lists, EricWF, delesley, aaron.ballman
Reviewed By: aaron.ballman
Subscribers: ed, aaron.ballman, joerg, emaste, cfe-commits
Differential Revision: https://reviews.llvm.org/D28520
llvm-svn: 293197
2017-01-27 02:37:18 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY _LIBCPP_NO_THREAD_SAFETY_ANALYSIS
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_condvar_timedwait(__libcpp_condvar_t *__cv, __libcpp_mutex_t *__m,
|
|
|
|
timespec *__ts);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
int __libcpp_condvar_destroy(__libcpp_condvar_t* __cv);
|
|
|
|
|
2017-01-03 20:59:50 +08:00
|
|
|
// Execute once
|
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
int __libcpp_execute_once(__libcpp_exec_once_flag *flag,
|
|
|
|
void (*init_routine)(void));
|
|
|
|
|
|
|
|
// Thread id
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
bool __libcpp_thread_id_equal(__libcpp_thread_id t1, __libcpp_thread_id t2);
|
2017-01-03 10:00:31 +08:00
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
bool __libcpp_thread_id_less(__libcpp_thread_id t1, __libcpp_thread_id t2);
|
|
|
|
|
|
|
|
// Thread
|
2017-01-16 20:19:54 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
bool __libcpp_thread_isnull(const __libcpp_thread_t *__t);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_thread_create(__libcpp_thread_t *__t, void *(*__func)(void *),
|
|
|
|
void *__arg);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
__libcpp_thread_id __libcpp_thread_get_current_id();
|
2017-01-03 10:00:31 +08:00
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 10:00:31 +08:00
|
|
|
__libcpp_thread_id __libcpp_thread_get_id(const __libcpp_thread_t *__t);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_thread_join(__libcpp_thread_t *__t);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_thread_detach(__libcpp_thread_t *__t);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
|
|
|
void __libcpp_thread_yield();
|
|
|
|
|
2017-02-09 17:31:41 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-02-09 22:12:29 +08:00
|
|
|
void __libcpp_thread_sleep_for(const chrono::nanoseconds& __ns);
|
2017-02-09 17:31:41 +08:00
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
// Thread local storage
|
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-07 11:07:45 +08:00
|
|
|
int __libcpp_tls_create(__libcpp_tls_key* __key,
|
|
|
|
void(_LIBCPP_TLS_DESTRUCTOR_CC* __at_exit)(void*));
|
2017-01-03 10:00:31 +08:00
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 10:00:31 +08:00
|
|
|
void *__libcpp_tls_get(__libcpp_tls_key __key);
|
|
|
|
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
_LIBCPP_THREAD_ABI_VISIBILITY
|
2017-01-03 20:59:50 +08:00
|
|
|
int __libcpp_tls_set(__libcpp_tls_key __key, void *__p);
|
[libcxx] Introduce an externally-threaded libc++ variant.
This patch further decouples libc++ from pthread, allowing libc++ to be built
against other threading systems. There are two main use cases:
- Building libc++ against a thread library other than pthreads.
- Building libc++ with an "external" thread API, allowing a separate library to
provide the implementation of that API.
The two use cases are quite similar, the second one being sligtly more
de-coupled than the first. The cmake option LIBCXX_HAS_EXTERNAL_THREAD_API
enables both kinds of builds. One needs to place an <__external_threading>
header file containing an implementation of the "libc++ thread API" declared
in the <__threading_support> header.
For the second use case, the implementation of the libc++ thread API can
delegate to a custom "external" thread API where the implementation of this
external API is provided in a seperate library. This mechanism allows toolchain
vendors to distribute a build of libc++ with a custom thread-porting-layer API
(which is the "external" API above), platform vendors (recipients of the
toolchain/libc++) are then required to provide their implementation of this API
to be linked with (end-user) C++ programs.
Note that the second use case still requires establishing the basic types that
get passed between the external thread library and the libc++ library
(e.g. __libcpp_mutex_t). These cannot be opaque pointer types (libc++ sources
won't compile otherwise). It should also be noted that the second use case can
have a slight performance penalty; as all the thread constructs need to cross a
library boundary through an additional function call.
When the header <__external_threading> is omitted, libc++ is built with the
"libc++ thread API" (declared in <__threading_support>) as the "external" thread
API (basic types are pthread based). An implementation (pthread based) of this
API is provided in test/support/external_threads.cpp, which is built into a
separate DSO and linked in when running the libc++ test suite. A test run
therefore demonstrates the second use case (less the intermediate custom API).
Differential revision: https://reviews.llvm.org/D21968
Reviewers: bcraig, compnerd, EricWF, mclow.lists
llvm-svn: 281179
2016-09-12 05:46:40 +08:00
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#if !defined(_LIBCPP_HAS_THREAD_LIBRARY_EXTERNAL) || \
|
|
|
|
defined(_LIBCPP_BUILDING_THREAD_LIBRARY_EXTERNAL)
|
|
|
|
|
|
|
|
#if defined(_LIBCPP_HAS_THREAD_API_PTHREAD)
|
2016-05-06 22:06:29 +08:00
|
|
|
|
2017-01-06 01:54:45 +08:00
|
|
|
int __libcpp_recursive_mutex_init(__libcpp_recursive_mutex_t *__m)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
pthread_mutexattr_t attr;
|
|
|
|
int __ec = pthread_mutexattr_init(&attr);
|
|
|
|
if (__ec)
|
|
|
|
return __ec;
|
|
|
|
__ec = pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
|
|
|
|
if (__ec) {
|
|
|
|
pthread_mutexattr_destroy(&attr);
|
|
|
|
return __ec;
|
|
|
|
}
|
|
|
|
__ec = pthread_mutex_init(__m, &attr);
|
|
|
|
if (__ec) {
|
|
|
|
pthread_mutexattr_destroy(&attr);
|
|
|
|
return __ec;
|
|
|
|
}
|
|
|
|
__ec = pthread_mutexattr_destroy(&attr);
|
|
|
|
if (__ec) {
|
|
|
|
pthread_mutex_destroy(__m);
|
|
|
|
return __ec;
|
|
|
|
}
|
|
|
|
return 0;
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-06 01:54:45 +08:00
|
|
|
int __libcpp_recursive_mutex_lock(__libcpp_recursive_mutex_t *__m)
|
|
|
|
{
|
|
|
|
return pthread_mutex_lock(__m);
|
|
|
|
}
|
|
|
|
|
2017-01-14 18:27:12 +08:00
|
|
|
bool __libcpp_recursive_mutex_trylock(__libcpp_recursive_mutex_t *__m)
|
2017-01-06 01:54:45 +08:00
|
|
|
{
|
2017-01-14 18:27:12 +08:00
|
|
|
return pthread_mutex_trylock(__m) == 0;
|
2017-01-06 01:54:45 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_recursive_mutex_unlock(__libcpp_mutex_t *__m)
|
|
|
|
{
|
|
|
|
return pthread_mutex_unlock(__m);
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_recursive_mutex_destroy(__libcpp_recursive_mutex_t *__m)
|
|
|
|
{
|
|
|
|
return pthread_mutex_destroy(__m);
|
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_mutex_lock(__libcpp_mutex_t *__m)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_mutex_lock(__m);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-14 18:27:12 +08:00
|
|
|
bool __libcpp_mutex_trylock(__libcpp_mutex_t *__m)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-14 18:27:12 +08:00
|
|
|
return pthread_mutex_trylock(__m) == 0;
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_mutex_unlock(__libcpp_mutex_t *__m)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_mutex_unlock(__m);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_mutex_destroy(__libcpp_mutex_t *__m)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_mutex_destroy(__m);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
// Condition Variable
|
|
|
|
int __libcpp_condvar_signal(__libcpp_condvar_t *__cv)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_cond_signal(__cv);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_condvar_broadcast(__libcpp_condvar_t *__cv)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_cond_broadcast(__cv);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_condvar_wait(__libcpp_condvar_t *__cv, __libcpp_mutex_t *__m)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_cond_wait(__cv, __m);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_condvar_timedwait(__libcpp_condvar_t *__cv, __libcpp_mutex_t *__m,
|
|
|
|
timespec *__ts)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_cond_timedwait(__cv, __m, __ts);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_condvar_destroy(__libcpp_condvar_t *__cv)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_cond_destroy(__cv);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 20:59:50 +08:00
|
|
|
// Execute once
|
|
|
|
int __libcpp_execute_once(__libcpp_exec_once_flag *flag,
|
|
|
|
void (*init_routine)(void)) {
|
|
|
|
return pthread_once(flag, init_routine);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Thread id
|
2016-05-06 22:06:29 +08:00
|
|
|
// Returns non-zero if the thread ids are equal, otherwise 0
|
|
|
|
bool __libcpp_thread_id_equal(__libcpp_thread_id t1, __libcpp_thread_id t2)
|
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_equal(t1, t2) != 0;
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
// Returns non-zero if t1 < t2, otherwise 0
|
|
|
|
bool __libcpp_thread_id_less(__libcpp_thread_id t1, __libcpp_thread_id t2)
|
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return t1 < t2;
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
// Thread
|
2017-01-16 20:19:54 +08:00
|
|
|
bool __libcpp_thread_isnull(const __libcpp_thread_t *__t) {
|
|
|
|
return *__t == 0;
|
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_thread_create(__libcpp_thread_t *__t, void *(*__func)(void *),
|
|
|
|
void *__arg)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_create(__t, 0, __func, __arg);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
__libcpp_thread_id __libcpp_thread_get_current_id()
|
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_self();
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
__libcpp_thread_id __libcpp_thread_get_id(const __libcpp_thread_t *__t)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return *__t;
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_thread_join(__libcpp_thread_t *__t)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_join(*__t, 0);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_thread_detach(__libcpp_thread_t *__t)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_detach(*__t);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
void __libcpp_thread_yield()
|
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
sched_yield();
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-02-09 17:31:41 +08:00
|
|
|
void __libcpp_thread_sleep_for(const chrono::nanoseconds& __ns)
|
|
|
|
{
|
|
|
|
using namespace chrono;
|
|
|
|
seconds __s = duration_cast<seconds>(__ns);
|
|
|
|
timespec __ts;
|
|
|
|
typedef decltype(__ts.tv_sec) ts_sec;
|
|
|
|
_LIBCPP_CONSTEXPR ts_sec __ts_sec_max = numeric_limits<ts_sec>::max();
|
|
|
|
|
|
|
|
if (__s.count() < __ts_sec_max)
|
|
|
|
{
|
|
|
|
__ts.tv_sec = static_cast<ts_sec>(__s.count());
|
|
|
|
__ts.tv_nsec = static_cast<decltype(__ts.tv_nsec)>((__ns - __s).count());
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
__ts.tv_sec = __ts_sec_max;
|
|
|
|
__ts.tv_nsec = 999999999; // (10^9 - 1)
|
|
|
|
}
|
|
|
|
|
|
|
|
while (nanosleep(&__ts, &__ts) == -1 && errno == EINTR);
|
|
|
|
}
|
|
|
|
|
2016-05-06 22:06:29 +08:00
|
|
|
// Thread local storage
|
2017-01-03 10:00:31 +08:00
|
|
|
int __libcpp_tls_create(__libcpp_tls_key *__key, void (*__at_exit)(void *))
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_key_create(__key, __at_exit);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
void *__libcpp_tls_get(__libcpp_tls_key __key)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 10:00:31 +08:00
|
|
|
return pthread_getspecific(__key);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-03 20:59:50 +08:00
|
|
|
int __libcpp_tls_set(__libcpp_tls_key __key, void *__p)
|
2016-05-06 22:06:29 +08:00
|
|
|
{
|
2017-01-03 20:59:50 +08:00
|
|
|
return pthread_setspecific(__key, __p);
|
2016-05-06 22:06:29 +08:00
|
|
|
}
|
|
|
|
|
2017-01-07 11:07:45 +08:00
|
|
|
#elif defined(_LIBCPP_HAS_THREAD_API_WIN32)
|
|
|
|
|
|
|
|
// Mutex
|
|
|
|
int __libcpp_recursive_mutex_init(__libcpp_recursive_mutex_t *__m)
|
|
|
|
{
|
|
|
|
InitializeCriticalSection(__m);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_recursive_mutex_lock(__libcpp_recursive_mutex_t *__m)
|
|
|
|
{
|
|
|
|
EnterCriticalSection(__m);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-01-14 18:27:12 +08:00
|
|
|
bool __libcpp_recursive_mutex_trylock(__libcpp_recursive_mutex_t *__m)
|
2017-01-07 11:07:45 +08:00
|
|
|
{
|
2017-01-14 18:27:12 +08:00
|
|
|
return TryEnterCriticalSection(__m) != 0;
|
2017-01-07 11:07:45 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_recursive_mutex_unlock(__libcpp_recursive_mutex_t *__m)
|
|
|
|
{
|
|
|
|
LeaveCriticalSection(__m);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_recursive_mutex_destroy(__libcpp_recursive_mutex_t *__m)
|
|
|
|
{
|
2017-01-10 12:18:47 +08:00
|
|
|
DeleteCriticalSection(__m);
|
2017-01-07 11:07:45 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_mutex_lock(__libcpp_mutex_t *__m)
|
|
|
|
{
|
|
|
|
AcquireSRWLockExclusive(__m);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-01-14 18:27:12 +08:00
|
|
|
bool __libcpp_mutex_trylock(__libcpp_mutex_t *__m)
|
2017-01-07 11:07:45 +08:00
|
|
|
{
|
2017-01-14 18:27:12 +08:00
|
|
|
return TryAcquireSRWLockExclusive(__m) != 0;
|
2017-01-07 11:07:45 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_mutex_unlock(__libcpp_mutex_t *__m)
|
|
|
|
{
|
|
|
|
ReleaseSRWLockExclusive(__m);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_mutex_destroy(__libcpp_mutex_t *__m)
|
|
|
|
{
|
|
|
|
static_cast<void>(__m);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Condition Variable
|
|
|
|
int __libcpp_condvar_signal(__libcpp_condvar_t *__cv)
|
|
|
|
{
|
|
|
|
WakeConditionVariable(__cv);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_condvar_broadcast(__libcpp_condvar_t *__cv)
|
|
|
|
{
|
|
|
|
WakeAllConditionVariable(__cv);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_condvar_wait(__libcpp_condvar_t *__cv, __libcpp_mutex_t *__m)
|
|
|
|
{
|
|
|
|
SleepConditionVariableSRW(__cv, __m, INFINITE, 0);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_condvar_timedwait(__libcpp_condvar_t *__cv, __libcpp_mutex_t *__m,
|
|
|
|
timespec *__ts)
|
|
|
|
{
|
|
|
|
using namespace _VSTD::chrono;
|
|
|
|
|
|
|
|
auto duration = seconds(__ts->tv_sec) + nanoseconds(__ts->tv_nsec);
|
|
|
|
auto abstime =
|
|
|
|
system_clock::time_point(duration_cast<system_clock::duration>(duration));
|
|
|
|
auto timeout_ms = duration_cast<milliseconds>(abstime - system_clock::now());
|
|
|
|
|
|
|
|
if (!SleepConditionVariableSRW(__cv, __m,
|
|
|
|
timeout_ms.count() > 0 ? timeout_ms.count()
|
|
|
|
: 0,
|
|
|
|
0))
|
2017-05-06 05:31:22 +08:00
|
|
|
{
|
|
|
|
auto __ec = GetLastError();
|
|
|
|
return __ec == ERROR_TIMEOUT ? ETIMEDOUT : __ec;
|
|
|
|
}
|
2017-01-07 11:07:45 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_condvar_destroy(__libcpp_condvar_t *__cv)
|
|
|
|
{
|
|
|
|
static_cast<void>(__cv);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Execute Once
|
|
|
|
static inline _LIBCPP_ALWAYS_INLINE BOOL CALLBACK
|
|
|
|
__libcpp_init_once_execute_once_thunk(PINIT_ONCE __init_once, PVOID __parameter,
|
|
|
|
PVOID *__context)
|
|
|
|
{
|
|
|
|
static_cast<void>(__init_once);
|
|
|
|
static_cast<void>(__context);
|
|
|
|
|
|
|
|
void (*init_routine)(void) = reinterpret_cast<void (*)(void)>(__parameter);
|
|
|
|
init_routine();
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_execute_once(__libcpp_exec_once_flag *__flag,
|
|
|
|
void (*__init_routine)(void))
|
|
|
|
{
|
|
|
|
if (!InitOnceExecuteOnce(__flag, __libcpp_init_once_execute_once_thunk,
|
|
|
|
reinterpret_cast<void *>(__init_routine), NULL))
|
|
|
|
return GetLastError();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Thread ID
|
|
|
|
bool __libcpp_thread_id_equal(__libcpp_thread_id __lhs,
|
|
|
|
__libcpp_thread_id __rhs)
|
|
|
|
{
|
|
|
|
return __lhs == __rhs;
|
|
|
|
}
|
|
|
|
|
|
|
|
bool __libcpp_thread_id_less(__libcpp_thread_id __lhs, __libcpp_thread_id __rhs)
|
|
|
|
{
|
|
|
|
return __lhs < __rhs;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Thread
|
|
|
|
struct __libcpp_beginthreadex_thunk_data
|
|
|
|
{
|
|
|
|
void *(*__func)(void *);
|
|
|
|
void *__arg;
|
|
|
|
};
|
|
|
|
|
2017-01-15 04:19:00 +08:00
|
|
|
static inline _LIBCPP_ALWAYS_INLINE unsigned WINAPI
|
2017-01-15 03:11:07 +08:00
|
|
|
__libcpp_beginthreadex_thunk(void *__raw_data)
|
2017-01-07 11:07:45 +08:00
|
|
|
{
|
2017-01-15 03:11:07 +08:00
|
|
|
auto *__data =
|
|
|
|
static_cast<__libcpp_beginthreadex_thunk_data *>(__raw_data);
|
|
|
|
auto *__func = __data->__func;
|
|
|
|
void *__arg = __data->__arg;
|
|
|
|
delete __data;
|
2017-01-15 04:19:00 +08:00
|
|
|
return static_cast<unsigned>(reinterpret_cast<uintptr_t>(__func(__arg)));
|
2017-01-07 11:07:45 +08:00
|
|
|
}
|
|
|
|
|
2017-01-16 20:19:54 +08:00
|
|
|
bool __libcpp_thread_isnull(const __libcpp_thread_t *__t) {
|
|
|
|
return *__t == 0;
|
|
|
|
}
|
|
|
|
|
2017-01-07 11:07:45 +08:00
|
|
|
int __libcpp_thread_create(__libcpp_thread_t *__t, void *(*__func)(void *),
|
|
|
|
void *__arg)
|
|
|
|
{
|
2017-01-15 03:11:07 +08:00
|
|
|
auto *__data = new __libcpp_beginthreadex_thunk_data;
|
|
|
|
__data->__func = __func;
|
|
|
|
__data->__arg = __arg;
|
|
|
|
|
2017-01-15 04:19:00 +08:00
|
|
|
*__t = reinterpret_cast<HANDLE>(_beginthreadex(nullptr, 0,
|
|
|
|
__libcpp_beginthreadex_thunk,
|
|
|
|
__data, 0, nullptr));
|
|
|
|
|
2017-01-07 11:07:45 +08:00
|
|
|
if (*__t)
|
|
|
|
return 0;
|
|
|
|
return GetLastError();
|
|
|
|
}
|
|
|
|
|
|
|
|
__libcpp_thread_id __libcpp_thread_get_current_id()
|
|
|
|
{
|
|
|
|
return GetCurrentThreadId();
|
|
|
|
}
|
|
|
|
|
|
|
|
__libcpp_thread_id __libcpp_thread_get_id(const __libcpp_thread_t *__t)
|
|
|
|
{
|
|
|
|
return GetThreadId(*__t);
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_thread_join(__libcpp_thread_t *__t)
|
|
|
|
{
|
|
|
|
if (WaitForSingleObjectEx(*__t, INFINITE, FALSE) == WAIT_FAILED)
|
|
|
|
return GetLastError();
|
|
|
|
if (!CloseHandle(*__t))
|
|
|
|
return GetLastError();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_thread_detach(__libcpp_thread_t *__t)
|
|
|
|
{
|
|
|
|
if (!CloseHandle(*__t))
|
|
|
|
return GetLastError();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
void __libcpp_thread_yield()
|
|
|
|
{
|
|
|
|
SwitchToThread();
|
|
|
|
}
|
|
|
|
|
2017-02-09 17:31:41 +08:00
|
|
|
void __libcpp_thread_sleep_for(const chrono::nanoseconds& __ns)
|
|
|
|
{
|
2017-02-19 03:28:43 +08:00
|
|
|
using namespace chrono;
|
2017-02-09 17:31:41 +08:00
|
|
|
// round-up to the nearest milisecond
|
2017-02-10 10:49:52 +08:00
|
|
|
milliseconds __ms =
|
|
|
|
duration_cast<milliseconds>(__ns + chrono::nanoseconds(999999));
|
2017-02-19 03:28:43 +08:00
|
|
|
// FIXME(compnerd) this should be an alertable sleep (WFSO or SleepEx)
|
|
|
|
Sleep(__ms.count());
|
2017-02-09 17:31:41 +08:00
|
|
|
}
|
|
|
|
|
2017-01-07 11:07:45 +08:00
|
|
|
// Thread Local Storage
|
|
|
|
int __libcpp_tls_create(__libcpp_tls_key* __key,
|
|
|
|
void(_LIBCPP_TLS_DESTRUCTOR_CC* __at_exit)(void*))
|
|
|
|
{
|
|
|
|
*__key = FlsAlloc(__at_exit);
|
|
|
|
if (*__key == FLS_OUT_OF_INDEXES)
|
|
|
|
return GetLastError();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
void *__libcpp_tls_get(__libcpp_tls_key __key)
|
|
|
|
{
|
|
|
|
return FlsGetValue(__key);
|
|
|
|
}
|
|
|
|
|
|
|
|
int __libcpp_tls_set(__libcpp_tls_key __key, void *__p)
|
|
|
|
{
|
|
|
|
if (!FlsSetValue(__key, __p))
|
|
|
|
return GetLastError();
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-01-03 10:00:31 +08:00
|
|
|
#endif // _LIBCPP_HAS_THREAD_API_PTHREAD
|
2016-05-06 22:06:29 +08:00
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#endif // !_LIBCPP_HAS_THREAD_LIBRARY_EXTERNAL || _LIBCPP_BUILDING_THREAD_LIBRARY_EXTERNAL
|
2016-05-06 22:06:29 +08:00
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
_LIBCPP_END_NAMESPACE_STD
|
2016-10-14 21:00:07 +08:00
|
|
|
|
2017-06-01 06:07:49 +08:00
|
|
|
_LIBCPP_POP_MACROS
|
|
|
|
|
2017-01-07 04:05:40 +08:00
|
|
|
#endif // !_LIBCPP_HAS_NO_THREADS
|
2016-05-06 22:06:29 +08:00
|
|
|
|
|
|
|
#endif // _LIBCPP_THREADING_SUPPORT
|