summaryrefslogtreecommitdiffstats
path: root/crypto/threads_win.c (follow)
Commit message (Expand)AuthorAgeFilesLines
* Always check CRYPTO_LOCK_{read,write}_lockRich Salz2021-03-141-2/+2
* Update copyright yearMatt Caswell2021-03-111-1/+1
* Use read/write locking on WindowsVincent Drake2021-03-111-2/+48
* Add some more CRYPTO_atomic functionsMatt Caswell2020-12-311-3/+16
* Update copyright yearMatt Caswell2020-04-231-1/+1
* Windows: Add type casting in CRYPTO_atomic_add to remove warningKochise2020-04-171-1/+1
* crypto/threads_win.c: fix preprocessor indentationDr. Matthias St. Pierre2019-09-111-3/+3
* drbg: ensure fork-safety without using a pthread_atfork handlerDr. Matthias St. Pierre2019-09-111-0/+4
* Avoid linking error for InitializeCriticalSectionAndSpinCount().Soujyu Tanaka2019-03-291-0/+4
* Following the license change, modify the boilerplates in crypto/Richard Levitte2018-12-061-1/+1
* crypto/threads_*: remove CRYPTO_atomic_{read|write}.Andy Polyakov2018-08-171-12/+0
* Save and restore the Windows error around TlsGetValue.David Benjamin2018-05-231-1/+20
* Update copyright yearRichard Levitte2018-04-171-1/+1
* Set error code if alloc returns NULLRich Salz2018-04-051-2/+5
* Return a value from atomic read on Windows.Pauli2017-10-111-1/+1
* Add atomic write callPauli2017-10-101-0/+6
* Add a CRYPTO_atomic_read call which allows an int variable to be readPauli2017-10-101-0/+6
* Add fork handlers, based on pthread_atforkRich Salz2017-06-291-0/+5
* Revert "Fixed deadlock in CRYPTO_THREAD_run_once for Windows"Matt Caswell2016-11-141-1/+1
* Fixed deadlock in CRYPTO_THREAD_run_once for WindowsDK2016-11-131-1/+1
* include/openssl: don't include <windows.h> in public headers.Andy Polyakov2016-07-081-0/+4
* Fix Windows 64 bit crashesMatt Caswell2016-05-211-23/+4
* Copyright consolidation 05/10Rich Salz2016-05-171-46/+6
* Fold threads.h into crypto.h making API publicViktor Dukhovni2016-05-161-1/+0
* Fix: CRYPTO_THREAD_run_onceMat2016-04-021-2/+2
* Fix return type for CRYPTO_THREAD_run_onceMat2016-03-101-1/+1
* GH773: Possible leak on CRYPTO_THREAD_lock_new failureFdaSilvaYY2016-03-041-1/+3
* Implement new multi-threading APIAlessandro Ghedini2016-02-261-0/+190