A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1965 
====================================================================== 
Reported By:                dannyniu
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1965
Category:                   System Interfaces
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
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:         
====================================================================== 
Date Submitted:             2025-12-21 06:49 UTC
Last Modified:              2026-01-15 17:16 UTC
====================================================================== 
Summary:                    Why isn't pthread_equal async-signal safe?
====================================================================== 

---------------------------------------------------------------------- 
 (0007363) geoffclare (manager) - 2026-01-15 17:16
 https://www.austingroupbugs.net/view.php?id=1965#c7363 
---------------------------------------------------------------------- 
Interpretation response
------------------------
The standard states that pthread_equal() need not be async-signal-safe, and
conforming applications must conform to this. However, concerns have been raised
about this which are being referred to the sponsor.

Rationale:
-------------
It is believed that no pthread interfaces were required to be async-signal-safe
in the original POSIX.1c threads amendment because the standard allowed
implementations to define pthread_t as a structure type.  However, now that the
standard requires pthread_kill() to be async-signal-safe, any such
implementation would need a way to pass a pthread_t structure to pthread_kill()
in an async-signal-safe manner and thus would be able to use the same method to
pass a pthread_t to pthread_equal().

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Add pthread_equal() to the list of async-signal-safe functions. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2025-12-21 06:49 dannyniu       New Issue                                    
2026-01-06 10:02 geoffclare     Note Added: 0007352                          
2026-01-10 04:26 dannyniu       Note Added: 0007362                          
2026-01-10 04:29 dannyniu       Note Edited: 0007362                         
2026-01-15 17:16 geoffclare     Note Added: 0007363                          
======================================================================


  • [1003.1(20... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group
    • [1003... Austin Group Issue Tracker via austin-group-l at The Open Group

Reply via email to