[SERVER-17455] Configure checks for __atomic and __sync should verify all required functions Created: 04/Mar/15 Updated: 07/Dec/16 Resolved: 22/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-jbr | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | See |
||||||||
| Sprint: | BUILD 2 04/24/15 | ||||||||
| Participants: | |||||||||
| Description |
|
We currently assume that the presence of _atomic_compare_exchange on a native width int means that the entire spectrum of __atomic* ops are available to us. We make similar assumptions for std::atomic or __sync. We should expand these tests to check for the presence of the entire API surface that we require. |
| Comments |
| Comment by Githook User [ 23/Apr/15 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |
| Comment by Githook User [ 22/Apr/15 ] |
|
Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}Message: |