- Title
- Potentially-concurrent actions within a signal handler
- Status
- c++17
- Section
- 6.10.2 [intro.multithread]
- Submitter
- Faisal Vali
Created on 2014-07-04.00:00:00 last changed 93 months ago
Messages
[Moved to DR at the November, 2016 meeting.]
Proposed resolution (November, 2015):
Change 6.10.2 [intro.multithread] paragraph 23 as follows:
Two actions are potentially concurrent if
they are performed by different threads, or
they are unsequenced,
andat least one is performed by a signal handler, and they are not both performed by the same signal handler invocation.
Notes from the October, 2015 meeting:
SG1 agrees that the existing wording should be amended to say something like “and they are not both performed by the same signal handler invocation.”
According to 6.10.2 [intro.multithread] paragraph 23,
Two actions are potentially concurrent if
they are performed by different threads, or
they are unsequenced, and at least one is performed by a signal handler.
This definition should exclude the case when both actions are performed by a signal handler.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-02-27 00:00:00 | admin | set | messages: + msg6154 |
| 2018-02-27 00:00:00 | admin | set | status: dr -> c++17 |
| 2017-02-06 00:00:00 | admin | set | status: review -> dr |
| 2015-11-10 00:00:00 | admin | set | messages: + msg5620 |
| 2015-11-10 00:00:00 | admin | set | messages: + msg5619 |
| 2015-11-10 00:00:00 | admin | set | status: concurrency -> review |
| 2014-07-04 00:00:00 | admin | create | |