We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I notice that atomicops.h implements atomic_*_fence on all _MSC_VER
Is there any benefit to make this conditional on say _MSC_VER < 1900 as I think its all present and correct in <atomic> for VS2015
<atomic>
The text was updated successfully, but these errors were encountered:
Probably a good idea. It might take a little while before I get around to it, though.
Sorry, something went wrong.
I made the change but no significant difference to benchmark numbers (MSVS 2015 CTP 5)
Incidentally profile guided optimisation improves the folly scores by 10% but rest are unaffected
Interesting, I never thought to try PGO.
I've committed the change (along with a blocking version of the queue) that uses the std:: fences on VS2012+. Thanks for opening this issue!
std::
No branches or pull requests
I notice that atomicops.h implements atomic_*_fence on all _MSC_VER
Is there any benefit to make this conditional on say _MSC_VER < 1900 as I think its all present and correct in
<atomic>
for VS2015The text was updated successfully, but these errors were encountered: