|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001625 |
[1003.1(2016/18)/Issue7+TC2] Base Definitions and Headers |
Objection |
Omission |
2023-01-04 02:18 |
2023-01-19 17:29 |
|
|
Reporter |
philip-guenther |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Resolved |
|
|
|
|
|
Name |
Philip Guenther |
|
Organization |
OpenBSD |
|
User Reference |
waitid |
|
Section |
waitid |
|
Page Number |
111 |
|
Line Number |
3066 |
|
Interp Status |
--- |
|
Final Accepted Text |
|
|
|
Summary |
0001625: waitid should be marked as aync-signal-safe and a memory-synchronization point |
|
Description |
(I only have issue 7 on hand, so section and line references will be off)
I believe that, historically, waitid() has been implemented in a manner similar to waitpid(), with an underlying system call and synchronization inside the kernel. Because of that, it has had the same sort of intrinsic behaviors described for wait() and waitpid() in XBD 4.12, "Memory Synchronization" and in XSH 2.4.3's for async-signal-safe functions. However, when it was added to the standard it was not included in those lists. |
|
Desired Action |
Add waitid() to the lists of both the memory synchronization and async-signal-safe functions.
|
| Tags |
tc3-2008 |
|
|
Attached Files |
|
|
|
Relationships 
