diff options
author | fluesvamp <105884371+fluesvamp@users.noreply.github.com> | 2022-08-13 03:40:41 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-08-13 03:40:41 (GMT) |
commit | 8281cbddc6f0fbc94f0c21cacfac79a2d4057a4b (patch) | |
tree | 07c49c697c305e2cf480c210f616212b3a4783a5 | |
parent | 187949ebf2ae36fcf0817a06f4a7637d0a8b7fc5 (diff) | |
download | cpython-8281cbddc6f0fbc94f0c21cacfac79a2d4057a4b.zip cpython-8281cbddc6f0fbc94f0c21cacfac79a2d4057a4b.tar.gz cpython-8281cbddc6f0fbc94f0c21cacfac79a2d4057a4b.tar.bz2 |
Fix typo in internal/pycore_atomic.h (GH-95939)
-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 { |