kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
e7b3ce58ad
boringssl/include/openssl/thread.h

175 lines
7.1 KiB
C
Raw Normal View History

Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young (eay@cryptsoft.com).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson (tjh@cryptsoft.com).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young (eay@cryptsoft.com)"
* The word 'cryptographic' can be left out if the rouines from the library
* being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence.] */
#ifndef OPENSSL_HEADER_THREAD_H
#define OPENSSL_HEADER_THREAD_H
Fix standalone build on Mac. CRYPTO_MUTEX was the wrong size. Fortunately, Apple was kind enough to define pthread_rwlock_t unconditionally, so we can be spared fighting with feature macros. Some of the stdlib.h removals were wrong and clang is pick about multiply-defined typedefs. Apparently that's a C11 thing? BUG=478598 Change-Id: Ibdcb8de9e5d83ca28e4c55b2979177d1ef0f9721 Reviewed-on: https://boringssl-review.googlesource.com/4404 Reviewed-by: Adam Langley <agl@google.com>
2015-04-20 16:32:12 +01:00
#include <sys/types.h>
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
#include <openssl/base.h>
#if defined(__cplusplus)
extern "C" {
#endif
Support Trusty, an embedded platform. Trusty doesn't have setjmp.h and nor does it have threads. Change-Id: I005f7a009a13e6632513be9fab2bbe62294519a4 Reviewed-on: https://boringssl-review.googlesource.com/4660 Reviewed-by: Adam Langley <agl@google.com>
2015-05-08 02:28:27 +01:00
#if defined(OPENSSL_NO_THREADS)
Resolve -Wextern-c-compat warnings with OPENSSL_NO_THREADS. C and C++ disagree on the sizes of empty structs, which can be rather bad for structs embedded in public headers. Stick a char in them to avoid issues. (It doesn't really matter for CRYPTO_STATIC_MUTEX, but it's easier to add a char in there too.) Thanks to Andrew Chi for reporting this issue. Change-Id: Ic54fff710b688decaa94848e9c7e1e73f0c58fd3 Reviewed-on: https://boringssl-review.googlesource.com/7760 Reviewed-by: David Benjamin <davidben@google.com>
2016-04-26 23:04:36 +01:00
typedef struct crypto_mutex_st {
char padding; /* Empty structs have different sizes in C and C++. */
} CRYPTO_MUTEX;
Support Trusty, an embedded platform. Trusty doesn't have setjmp.h and nor does it have threads. Change-Id: I005f7a009a13e6632513be9fab2bbe62294519a4 Reviewed-on: https://boringssl-review.googlesource.com/4660 Reviewed-by: Adam Langley <agl@google.com>
2015-05-08 02:28:27 +01:00
#elif defined(OPENSSL_WINDOWS)
crypto: add mutexes. Prior to this, BoringSSL was using OpenSSL's technique of having users register a callback for locking operation. This change adds native mutex support. Since mutexes often need to be in objects that are exposed via public headers, the non-static mutexes are defined in thread.h. However, on Windows we don't want to #include windows.h for CRITICAL_SECTION and, on Linux, pthread.h doesn't define pthread_rwlock_t unless the feature flags are set correctly—something that we can't control in general for public header files. Thus, on both platforms, the mutex is defined as a uint8_t[] of equal or greater size and we depend on static asserts to ensure that everything works out ok. Change-Id: Iafec17ae7e3422325e587878a5384107ec6647ab Reviewed-on: https://boringssl-review.googlesource.com/4321 Reviewed-by: Adam Langley <agl@google.com>
2015-04-13 19:04:08 +01:00
/* CRYPTO_MUTEX can appear in public header files so we really don't want to
* pull in windows.h. It's statically asserted that this structure is large
Switch Windows CRYPTO_MUTEX implementation to SRWLOCK. Now that we no longer support Windows XP, this is available. Unfortunately, the public header version of CRYPTO_MUTEX means we still can't easily merge CRYPTO_MUTEX and CRYPTO_STATIC_MUTEX. BUG=37 Change-Id: If309de3f06e0854c505083b72fd64d1dbb3f4563 Reviewed-on: https://boringssl-review.googlesource.com/8081 Reviewed-by: Adam Langley <agl@google.com>
2016-05-24 16:41:11 +01:00
* enough to contain a Windows SRWLOCK by thread_win.c. */
crypto: add mutexes. Prior to this, BoringSSL was using OpenSSL's technique of having users register a callback for locking operation. This change adds native mutex support. Since mutexes often need to be in objects that are exposed via public headers, the non-static mutexes are defined in thread.h. However, on Windows we don't want to #include windows.h for CRITICAL_SECTION and, on Linux, pthread.h doesn't define pthread_rwlock_t unless the feature flags are set correctly—something that we can't control in general for public header files. Thus, on both platforms, the mutex is defined as a uint8_t[] of equal or greater size and we depend on static asserts to ensure that everything works out ok. Change-Id: Iafec17ae7e3422325e587878a5384107ec6647ab Reviewed-on: https://boringssl-review.googlesource.com/4321 Reviewed-by: Adam Langley <agl@google.com>
2015-04-13 19:04:08 +01:00
typedef union crypto_mutex_st {
Switch Windows CRYPTO_MUTEX implementation to SRWLOCK. Now that we no longer support Windows XP, this is available. Unfortunately, the public header version of CRYPTO_MUTEX means we still can't easily merge CRYPTO_MUTEX and CRYPTO_STATIC_MUTEX. BUG=37 Change-Id: If309de3f06e0854c505083b72fd64d1dbb3f4563 Reviewed-on: https://boringssl-review.googlesource.com/8081 Reviewed-by: Adam Langley <agl@google.com>
2016-05-24 16:41:11 +01:00
void *handle;
crypto: add mutexes. Prior to this, BoringSSL was using OpenSSL's technique of having users register a callback for locking operation. This change adds native mutex support. Since mutexes often need to be in objects that are exposed via public headers, the non-static mutexes are defined in thread.h. However, on Windows we don't want to #include windows.h for CRITICAL_SECTION and, on Linux, pthread.h doesn't define pthread_rwlock_t unless the feature flags are set correctly—something that we can't control in general for public header files. Thus, on both platforms, the mutex is defined as a uint8_t[] of equal or greater size and we depend on static asserts to ensure that everything works out ok. Change-Id: Iafec17ae7e3422325e587878a5384107ec6647ab Reviewed-on: https://boringssl-review.googlesource.com/4321 Reviewed-by: Adam Langley <agl@google.com>
2015-04-13 19:04:08 +01:00
} CRYPTO_MUTEX;
Fix standalone build on Mac. CRYPTO_MUTEX was the wrong size. Fortunately, Apple was kind enough to define pthread_rwlock_t unconditionally, so we can be spared fighting with feature macros. Some of the stdlib.h removals were wrong and clang is pick about multiply-defined typedefs. Apparently that's a C11 thing? BUG=478598 Change-Id: Ibdcb8de9e5d83ca28e4c55b2979177d1ef0f9721 Reviewed-on: https://boringssl-review.googlesource.com/4404 Reviewed-by: Adam Langley <agl@google.com>
2015-04-20 16:32:12 +01:00
#elif defined(__MACH__) && defined(__APPLE__)
typedef pthread_rwlock_t CRYPTO_MUTEX;
crypto: add mutexes. Prior to this, BoringSSL was using OpenSSL's technique of having users register a callback for locking operation. This change adds native mutex support. Since mutexes often need to be in objects that are exposed via public headers, the non-static mutexes are defined in thread.h. However, on Windows we don't want to #include windows.h for CRITICAL_SECTION and, on Linux, pthread.h doesn't define pthread_rwlock_t unless the feature flags are set correctly—something that we can't control in general for public header files. Thus, on both platforms, the mutex is defined as a uint8_t[] of equal or greater size and we depend on static asserts to ensure that everything works out ok. Change-Id: Iafec17ae7e3422325e587878a5384107ec6647ab Reviewed-on: https://boringssl-review.googlesource.com/4321 Reviewed-by: Adam Langley <agl@google.com>
2015-04-13 19:04:08 +01:00
#else
/* It is reasonable to include pthread.h on non-Windows systems, however the
* |pthread_rwlock_t| that we need is hidden under feature flags, and we can't
* ensure that we'll be able to get it. It's statically asserted that this
* structure is large enough to contain a |pthread_rwlock_t| by
* thread_pthread.c. */
typedef union crypto_mutex_st {
double alignment;
uint8_t padding[3*sizeof(int) + 5*sizeof(unsigned) + 16 + 8];
} CRYPTO_MUTEX;
#endif
Add infrastructure for reference counts. OpenSSL has traditionally done reference counting with |int|s and the |CRYPTO_add| function. Unless a special callback is installed (rare), this is implemented by doing the reference count operations under a lock. This change adds infrastructure for handling reference counts and uses atomic operations when C11 support is available. Change-Id: Ia023ce432319efd00f77a7340da27d16ee4b63c3 Reviewed-on: https://boringssl-review.googlesource.com/4771 Reviewed-by: Adam Langley <agl@google.com>
2015-05-15 20:01:29 +01:00
/* CRYPTO_refcount_t is the type of a reference count.
*
* Since some platforms use C11 atomics to access this, it should have the
* _Atomic qualifier. However, this header is included by C++ programs as well
* as C code that might not set -std=c11. So, in practice, it's not possible to
* do that. Instead we statically assert that the size and native alignment of
* a plain uint32_t and an _Atomic uint32_t are equal in refcount_c11.c. */
typedef uint32_t CRYPTO_refcount_t;
crypto: add mutexes. Prior to this, BoringSSL was using OpenSSL's technique of having users register a callback for locking operation. This change adds native mutex support. Since mutexes often need to be in objects that are exposed via public headers, the non-static mutexes are defined in thread.h. However, on Windows we don't want to #include windows.h for CRITICAL_SECTION and, on Linux, pthread.h doesn't define pthread_rwlock_t unless the feature flags are set correctly—something that we can't control in general for public header files. Thus, on both platforms, the mutex is defined as a uint8_t[] of equal or greater size and we depend on static asserts to ensure that everything works out ok. Change-Id: Iafec17ae7e3422325e587878a5384107ec6647ab Reviewed-on: https://boringssl-review.googlesource.com/4321 Reviewed-by: Adam Langley <agl@google.com>
2015-04-13 19:04:08 +01:00
Remove leftovers of the old-style locks. At this point, none of these functions or macros are used so they can just be deleted. Change-Id: I8ed1aae7a252e886864bf43e3096eff2228183cd Reviewed-on: https://boringssl-review.googlesource.com/4777 Reviewed-by: Adam Langley <agl@google.com>
2015-05-16 00:00:15 +01:00
/* Deprecated functions */
Fix up whitespace in headers for doc.go. Also, set sensible defaults for the command-line arguments to doc.go. Change-Id: Iefd2ade4c9095489efa0ae1059007593fc84923a
2015-04-09 01:32:55 +01:00
Readd CRYPTO_{LOCK|UNLOCK|READ|WRITE}. These defines are part of the the locking callbacks which have been removed. However, code that still tries to provide locking callbacks will need these values to compile. The locking callback that such code tries to install will be ignored, but that's harmless since BoringSSL handles locking itself now. Change-Id: Ic84da8b52020ccd3ecc8913b4e41d366690c7649
2015-05-27 23:46:26 +01:00
/* These defines do nothing but are provided to make old code easier to
* compile. */
#define CRYPTO_LOCK 1
#define CRYPTO_UNLOCK 2
#define CRYPTO_READ 4
#define CRYPTO_WRITE 8
Remove leftovers of the old-style locks. At this point, none of these functions or macros are used so they can just be deleted. Change-Id: I8ed1aae7a252e886864bf43e3096eff2228183cd Reviewed-on: https://boringssl-review.googlesource.com/4777 Reviewed-by: Adam Langley <agl@google.com>
2015-05-16 00:00:15 +01:00
/* CRYPTO_num_locks returns one. (This is non-zero that callers who allocate
* sizeof(lock) times this value don't get zero and then fail because malloc(0)
* returned NULL.) */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT int CRYPTO_num_locks(void);
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
Remove leftovers of the old-style locks. At this point, none of these functions or macros are used so they can just be deleted. Change-Id: I8ed1aae7a252e886864bf43e3096eff2228183cd Reviewed-on: https://boringssl-review.googlesource.com/4777 Reviewed-by: Adam Langley <agl@google.com>
2015-05-16 00:00:15 +01:00
/* CRYPTO_set_locking_callback does nothing. */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT void CRYPTO_set_locking_callback(
void (*func)(int mode, int lock_num, const char *file, int line));
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
Remove leftovers of the old-style locks. At this point, none of these functions or macros are used so they can just be deleted. Change-Id: I8ed1aae7a252e886864bf43e3096eff2228183cd Reviewed-on: https://boringssl-review.googlesource.com/4777 Reviewed-by: Adam Langley <agl@google.com>
2015-05-16 00:00:15 +01:00
/* CRYPTO_set_add_lock_callback does nothing. */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT void CRYPTO_set_add_lock_callback(int (*func)(
int *num, int amount, int lock_num, const char *file, int line));
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
Remove leftovers of the old-style locks. At this point, none of these functions or macros are used so they can just be deleted. Change-Id: I8ed1aae7a252e886864bf43e3096eff2228183cd Reviewed-on: https://boringssl-review.googlesource.com/4777 Reviewed-by: Adam Langley <agl@google.com>
2015-05-16 00:00:15 +01:00
/* CRYPTO_get_lock_name returns a fixed, dummy string. */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT const char *CRYPTO_get_lock_name(int lock_num);
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
Remove leftovers of the old-style locks. At this point, none of these functions or macros are used so they can just be deleted. Change-Id: I8ed1aae7a252e886864bf43e3096eff2228183cd Reviewed-on: https://boringssl-review.googlesource.com/4777 Reviewed-by: Adam Langley <agl@google.com>
2015-05-16 00:00:15 +01:00
/* CRYPTO_THREADID_set_callback returns one. */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT int CRYPTO_THREADID_set_callback(
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
void (*threadid_func)(CRYPTO_THREADID *threadid));
Get rid of the THREADID stuff. Now that ERR is using thread-local storage, there's very little that the THREADID code is doing and it can be turned into stub functions. Change-Id: I668613fec39b26c894d029b10a8173c3055f6019
2015-04-01 02:55:53 +01:00
/* CRYPTO_THREADID_set_numeric does nothing. */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT void CRYPTO_THREADID_set_numeric(CRYPTO_THREADID *id,
unsigned long val);
Get rid of the THREADID stuff. Now that ERR is using thread-local storage, there's very little that the THREADID code is doing and it can be turned into stub functions. Change-Id: I668613fec39b26c894d029b10a8173c3055f6019
2015-04-01 02:55:53 +01:00
/* CRYPTO_THREADID_set_pointer does nothing. */
Add visibility rules. This change marks public symbols as dynamically exported. This means that it becomes viable to build a shared library of libcrypto and libssl with -fvisibility=hidden. On Windows, one not only needs to mark functions for export in a component, but also for import when using them from a different component. Because of this we have to build with |BORINGSSL_IMPLEMENTATION| defined when building the code. Other components, when including our headers, won't have that defined and then the |OPENSSL_EXPORT| tag becomes an import tag instead. See the #defines in base.h In the asm code, symbols are now hidden by default and those that need to be exported are wrapped by a C function. In order to support Chromium, a couple of libssl functions were moved to ssl.h from ssl_locl.h: ssl_get_new_session and ssl_update_cache. Change-Id: Ib4b76e2f1983ee066e7806c24721e8626d08a261 Reviewed-on: https://boringssl-review.googlesource.com/1350 Reviewed-by: Adam Langley <agl@google.com>
2014-07-31 00:02:14 +01:00
OPENSSL_EXPORT void CRYPTO_THREADID_set_pointer(CRYPTO_THREADID *id, void *ptr);
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
Get rid of the THREADID stuff. Now that ERR is using thread-local storage, there's very little that the THREADID code is doing and it can be turned into stub functions. Change-Id: I668613fec39b26c894d029b10a8173c3055f6019
2015-04-01 02:55:53 +01:00
/* CRYPTO_THREADID_current does nothing. */
OPENSSL_EXPORT void CRYPTO_THREADID_current(CRYPTO_THREADID *id);
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
/* Private functions.
*
* Some old code calls these functions and so no-op implementations are
* provided.
*
* TODO(fork): cleanup callers and remove. */
Also export some deprecated functions. I didn't mark these functions as OPENSSL_EXPORT in the first place because I was hoping that they wouldn't be needed. However, WebRTC and libjingle are using them. Change-Id: I7a9de770a0a2213e99725b9b5ac7d3d13754ebfd
2014-08-01 18:33:29 +01:00
OPENSSL_EXPORT void CRYPTO_set_id_callback(unsigned long (*func)(void));
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
typedef struct {
int references;
struct CRYPTO_dynlock_value *data;
} CRYPTO_dynlock;
Also export some deprecated functions. I didn't mark these functions as OPENSSL_EXPORT in the first place because I was hoping that they wouldn't be needed. However, WebRTC and libjingle are using them. Change-Id: I7a9de770a0a2213e99725b9b5ac7d3d13754ebfd
2014-08-01 18:33:29 +01:00
OPENSSL_EXPORT void CRYPTO_set_dynlock_create_callback(
struct CRYPTO_dynlock_value *(*dyn_create_function)(const char *file,
int line));
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
Also export some deprecated functions. I didn't mark these functions as OPENSSL_EXPORT in the first place because I was hoping that they wouldn't be needed. However, WebRTC and libjingle are using them. Change-Id: I7a9de770a0a2213e99725b9b5ac7d3d13754ebfd
2014-08-01 18:33:29 +01:00
OPENSSL_EXPORT void CRYPTO_set_dynlock_lock_callback(void (*dyn_lock_function)(
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
int mode, struct CRYPTO_dynlock_value *l, const char *file, int line));
Also export some deprecated functions. I didn't mark these functions as OPENSSL_EXPORT in the first place because I was hoping that they wouldn't be needed. However, WebRTC and libjingle are using them. Change-Id: I7a9de770a0a2213e99725b9b5ac7d3d13754ebfd
2014-08-01 18:33:29 +01:00
OPENSSL_EXPORT void CRYPTO_set_dynlock_destroy_callback(
void (*dyn_destroy_function)(struct CRYPTO_dynlock_value *l,
const char *file, int line));
Move public headers to include/openssl/ Previously, public headers lived next to the respective code and there were symlinks from include/openssl to them. This doesn't work on Windows. This change moves the headers to live in include/openssl. In cases where some symlinks pointed to the same header, I've added a file that just includes the intended target. These cases are all for backwards-compat. Change-Id: I6e285b74caf621c644b5168a4877db226b07fd92 Reviewed-on: https://boringssl-review.googlesource.com/1180 Reviewed-by: David Benjamin <davidben@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
2014-07-14 23:28:14 +01:00
#if defined(__cplusplus)
} /* extern C */
#endif
#endif /* OPENSSL_HEADER_THREAD_H */
Reference in New Issue Copy Permalink