Work around warnings building Google Benchmark w/Clang #2
Conversation
This file contains 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
This should allow the HAVE_THREAD_SAFETY_ATTRIBUTES check to succeed and subsequently annotate the mutex functions properly and resolve the build warnings we're seeing in the clang/libcxx nightly builds. Hopefully there will be an official fix for the issue soon. Signed-off-by: Scott K Logan <logans@cottsay.net>
dirk-thomas
approved these changes
Jul 16, 2020
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.
This should allow the HAVE_THREAD_SAFETY_ATTRIBUTES check to succeed and subsequently annotate the mutex functions properly and resolve the build warnings we're seeing in the clang/libcxx nightly builds.
Hopefully there will be an official fix for the issue soon.