use legacy atomics on gcc < 5 #893
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vector-of-bool
approved these changes
Nov 11, 2021
kevinAlbs
approved these changes
Nov 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So, it turns out that we need to use legacy atomics on all gcc 4.x versions. The original change in #889 still results in build failures on Debian 8 (gcc 4.9). It seems that using the new
__atomicbuilt-ins requires setting-std=c11. It is not clear that we want to require that for legacy platforms, so expanding the check in this way seems like the better way.Full patch build (filtered down to the Debian 8 variant): https://spruce.mongodb.com/version/618d9bcd0305b93ba3051410/tasks?page=0&variant=%5Egcc49%24