Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(22587)

Side by Side Diff: Modules/hashlib.h

Issue 16113: Add SHA-3 (Keccak) support
Patch Set: Created 6 years, 11 months ago
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View unified diff | Download patch
OLDNEW
1 /* Common code for use by all hashlib related modules. */ 1 /* Common code for use by all hashlib related modules. */
2 2
3 /* 3 /*
4 * Given a PyObject* obj, fill in the Py_buffer* viewp with the result 4 * Given a PyObject* obj, fill in the Py_buffer* viewp with the result
5 * of PyObject_GetBuffer. Sets and exception and issues a return NULL 5 * of PyObject_GetBuffer. Sets and exception and issues a return NULL
6 * on any errors. 6 * on any errors.
7 */ 7 */
8 #define GET_BUFFER_VIEW_OR_ERROUT(obj, viewp) do { \ 8 #define GET_BUFFER_VIEW_OR_ERROUT(obj, viewp) do { \
9 if (PyUnicode_Check((obj))) { \ 9 if (PyUnicode_Check((obj))) { \
10 PyErr_SetString(PyExc_TypeError, \ 10 PyErr_SetString(PyExc_TypeError, \
11 "Unicode-objects must be encoded before hashing");\ 11 "Unicode-objects must be encoded before hashing");\
12 return NULL; \ 12 return NULL; \
13 } \ 13 } \
14 if (!PyObject_CheckBuffer((obj))) { \ 14 if (!PyObject_CheckBuffer((obj))) { \
15 PyErr_SetString(PyExc_TypeError, \ 15 PyErr_SetString(PyExc_TypeError, \
16 "object supporting the buffer API required"); \ 16 "object supporting the buffer API required"); \
17 return NULL; \ 17 return NULL; \
18 } \ 18 } \
19 if (PyObject_GetBuffer((obj), (viewp), PyBUF_SIMPLE) == -1) { \ 19 if (PyObject_GetBuffer((obj), (viewp), PyBUF_SIMPLE) == -1) { \
20 return NULL; \ 20 return NULL; \
21 } \ 21 } \
22 if ((viewp)->ndim > 1) { \ 22 if ((viewp)->ndim > 1) { \
23 PyErr_SetString(PyExc_BufferError, \ 23 PyErr_SetString(PyExc_BufferError, \
24 "Buffer must be single dimension"); \ 24 "Buffer must be single dimension"); \
25 PyBuffer_Release((viewp)); \ 25 PyBuffer_Release((viewp)); \
26 return NULL; \ 26 return NULL; \
27 } \ 27 } \
28 } while(0); 28 } while(0);
29
30 /*
31 * Helper code to synchronize access to the hash object when the GIL is
32 * released around a CPU consuming hashlib operation. All code paths that
33 * access a mutable part of obj must be enclosed in a ENTER_HASHLIB /
34 * LEAVE_HASHLIB block or explicitly acquire and release the lock inside
35 * a PY_BEGIN / END_ALLOW_THREADS block if they wish to release the GIL for
36 * an operation.
37 */
38
39 #ifdef WITH_THREAD
40 #include "pythread.h"
41 #define ENTER_HASHLIB(obj) \
42 if ((obj)->lock) { \
43 if (!PyThread_acquire_lock((obj)->lock, 0)) { \
44 Py_BEGIN_ALLOW_THREADS \
45 PyThread_acquire_lock((obj)->lock, 1); \
46 Py_END_ALLOW_THREADS \
47 } \
48 }
49 #define LEAVE_HASHLIB(obj) \
50 if ((obj)->lock) { \
51 PyThread_release_lock((obj)->lock); \
52 }
53 #else
54 #define ENTER_HASHLIB(obj)
55 #define LEAVE_HASHLIB(obj)
56 #endif
57
58 /* Threshold size for initial GIL release. */
59 #define GIL_RELEASE_MINSIZE 2048
AntoinePitrou 2012/10/05 23:27:10 You probably want a larger value, say 8192 or 1638
gregory.p.smith 2012/10/05 23:32:14 processor speeds that software runs on varies all
christian.heimes 2012/10/05 23:37:05 There is the constant, great! I'll move HASHLIB_GI
OLDNEW
« no previous file with comments | « Lib/test/test_hashlib.py ('k') | Modules/_hashopenssl.c » ('j') | Modules/_sha3/sha3module.c » ('J')

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+