0001965: Why isn't pthread_equal async-signal safe?

ID	Project	Category	View Status	Date Submitted	Last Update

0001965	1003.1(2024)/Issue8	System Interfaces	public	2025-12-21 06:49	2025-12-21 06:49

Reporter	dannyniu	Assigned To
Priority	normal	Severity	Editorial	Type	Clarification Requested
Status	New	Resolution	Open

Name	DannyNiu/NJF
Organization
User Reference
Section	<pthread.h> `pthread_equal`
Page Number	239, 1722
Line Number	11576, 57189-57227
Interp Status
Final Accepted Text


Summary	0001965: Why isn't pthread_equal async-signal safe?
Description	Currently there are 4 pthread_* functions that're async-signal-safe, including pthread_self. IMHO, there's no reason to not make pthread_equal safe, unless during some thread control operation, some function would modify the internal data structure if pthread_t is not a scalar. Additionally, unless some implementation _does_ alter pthread_t handle, I think it's perfectly fine to require that the arguments be const-qualified, or that pthread_t be a pointer to a const-qualified data structure.
Desired Action	Clarify whether and why pthread_equals isn't an async-signal-safe function.
Tags	No tags attached.

Date Modified	Username	Field	Change
2025-12-21 06:49	dannyniu	New Issue