summaryrefslogtreecommitdiffstats
path: root/Python/bytecodes.c
diff options
context:
space:
mode:
authorVincent Fazio <vfazio@gmail.com>2025-04-04 14:31:37 (GMT)
committerGitHub <noreply@github.com>2025-04-04 14:31:37 (GMT)
commit72123063ddee84bb2c9d591a23f420997e35af5a (patch)
tree2c27d8986caccf45a496da7565054e784a6f9158 /Python/bytecodes.c
parent345baa77ba2ce3b8ea8f2fad84754e5cc0b10938 (diff)
downloadcpython-72123063ddee84bb2c9d591a23f420997e35af5a.zip
cpython-72123063ddee84bb2c9d591a23f420997e35af5a.tar.gz
cpython-72123063ddee84bb2c9d591a23f420997e35af5a.tar.bz2
gh-130115: fix thread identifiers for 32-bit musl (#130391)
CPython's pthread-based thread identifier relies on pthread_t being able to be represented as an unsigned integer type. This is true in most Linux libc implementations where it's defined as an unsigned long, however musl typedefs it as a struct *. If the pointer has the high bit set and is cast to PyThread_ident_t, the resultant value can be sign-extended [0]. This can cause issues when comparing against threading._MainThread's identifier. The main thread's identifier value is retrieved via _get_main_thread_ident which is backed by an unsigned long which truncates sign extended bits. >>> hex(threading.main_thread().ident) '0xb6f33f3c' >>> hex(threading.current_thread().ident) '0xffffffffb6f33f3c' Work around this by conditionally compiling in some code for non-glibc based Linux platforms that are at risk of sign-extension to return a PyLong based on the main thread's unsigned long thread identifier if the current thread is the main thread. [0]: https://gcc.gnu.org/onlinedocs/gcc-14.2.0/gcc/Arrays-and-pointers-implementation.html --------- Signed-off-by: Vincent Fazio <vfazio@gmail.com>
Diffstat (limited to 'Python/bytecodes.c')
0 files changed, 0 insertions, 0 deletions