[SERVER-16363] Remove all volatile storage types from server source code Created: 01/Dec/14 Updated: 05/Apr/17 Resolved: 29/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2017-01-23 |
| Participants: |
| Description |
|
As of C++11, volatile storage types very clearly exist only for memory mapped registers (device drivers), and do not have any special semantics for multithreaded code. As a result, we should remove all uses of volatile storage types. At the same time, we should adjust the flags we pass to MSVC to include /volatile:iso, to make its behavior consistent with the standard and to improve performance. |
| Comments |
| Comment by Githook User [ 29/Dec/16 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |