Notes |
(0004091)
carlos (reporter)
2018-08-24 20:23
|
The same question should be raised for sigpause, which does an unmask and wait also. |
|
(0004332)
nick (manager)
2019-03-18 15:49
edited on: 2019-03-18 15:49
|
Interpretation response
------------------------
The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.
Rationale:
-------------
The intention of the committee was to make this function atomic, but the wording did not make this clear.
Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Change page 1984 lines 63848-63849 from:
The sigsuspend( ) function shall replace the current signal mask of the calling thread with the set of signals pointed to by sigmask and then suspend the thread until delivery of a signal whose action is either to execute a signal-catching function or to terminate the process.
to:
The sigsuspend( ) function shall atomically both replace the current signal mask of the calling thread with the set of signals pointed to by sigmask and suspend the thread until delivery of a signal whose action is either to execute a signal-catching function or to terminate the process.
Change on p1964 lines 63342-63343
The sigpause( ) function shall remove sig from the signal mask of the calling process and suspend the calling process until a signal is received.
to:
The sigpause( ) function shall atomically both remove sig from the signal mask of the calling process and suspend the calling process until a signal is delivered whose action is either to execute a signal-catching function or to terminate the process.
|
|
(0004343)
agadmin (administrator)
2019-03-21 15:47
|
Interpretation Proposed: 21st March 2019 |
|
(0004389)
agadmin (administrator)
2019-05-09 09:27
|
Interpretation approved: 9 May 2019 |
|