Issue 2143: ios_base::xalloc should be thread-safe

Title: ios_base::xalloc should be thread-safe
Status: c++14
Section: [ios.base]
Submitter: Alberto Ganesh Barbati

Created on 2012-03-14.00:00:00 last changed 130 months ago

Messages

msg6657 (view)

Date: 2013-09-29.10:45:42

Proposed resolution:

This wording is relative to N3376.

In [ios.base.storage] add a new paragraph after paragraph 1:
```
static int xalloc();
```
-1- Returns: index ++.
-?- Remarks: Concurrent access to this function by multiple threads shall not result in a data race ([intro.multithread]).

msg6505 (view)

Date: 2013-09-15.00:00:00

[ 2013-09-29, Chicago ]

Apply to Working Paper

msg6064 (view)

Date: 2013-04-15.00:00:00

[ 2013-04-20, Bristol ]

Unanimous.

Resolution: move tentatively ready. (Inform Bill about this issue.)

msg6063 (view)

Date: 2012-03-19.18:57:47

The static function ios_base::xalloc() could be called from multiple threads and is not covered by [res.on.objects] and [res.on.data.races]. Adding a thread-safety requirement should not impose a significant burden on implementations, as the function can be easily implemented with hopefully lock-free atomics.

History
Date	User	Action	Args
2014-02-20 13:20:35	admin	set	status: wp -> c++14
2013-09-29 10:45:42	admin	set	messages: + msg6657
2013-09-29 10:45:42	admin	set	status: voting -> wp
2013-09-23 13:24:31	admin	set	status: ready -> voting
2013-05-20 16:25:01	admin	set	messages: + msg6505
2013-05-20 16:25:01	admin	set	status: new -> ready
2012-03-18 12:23:33	admin	set	messages: + msg6064
2012-03-14 00:00:00	admin	create