diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2022-08-13 04:05:37 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-13 04:05:37 (GMT) |
| commit | 83bde57f6e549b017116d2c89ef427ea0fb8dad4 (patch) | |
| tree | 706e6a80ad555313cb6cb0607f93998a7e002ae1 | |
| parent | 9fbc81760e8765f7520929acc5af7874aeccb0c1 (diff) | |
| download | cpython-83bde57f6e549b017116d2c89ef427ea0fb8dad4.zip cpython-83bde57f6e549b017116d2c89ef427ea0fb8dad4.tar.gz cpython-83bde57f6e549b017116d2c89ef427ea0fb8dad4.tar.bz2 | |
Fix typo in internal/pycore_atomic.h (GH-95939)
(cherry picked from commit 8281cbddc6f0fbc94f0c21cacfac79a2d4057a4b)
Co-authored-by: fluesvamp <105884371+fluesvamp@users.noreply.github.com>
| -rw-r--r-- | Include/internal/pycore_atomic.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Include/internal/pycore_atomic.h b/Include/internal/pycore_atomic.h index 3d42e54..425d69f 100644 --- a/Include/internal/pycore_atomic.h +++ b/Include/internal/pycore_atomic.h @@ -236,7 +236,7 @@ _Py_ANNOTATE_MEMORY_ORDER(const volatile void *address, _Py_memory_order order) in hardware they will fall back to a full memory barrier as well. This might affect performance but likely only in some very specific and - hard to meassure scenario. + hard to measure scenario. */ #if defined(_M_IX86) || defined(_M_X64) typedef enum _Py_memory_order { |