-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Use new 64-bit interlocked intrinsics on x86 #986
New issue
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
Use new 64-bit interlocked intrinsics on x86 #986
Conversation
|
Wow, some tests do fail. Will take a look |
|
So actually clang does not support them. |
Co-authored-by: Stephan T. Lavavej <stl@nuwen.net>
|
Filled LLVM-46595. |
StephanTLavavej
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for filing the LLVM bug/feature request!
We haven't repeated bug numbers in #else arrow comments before, but (1) I think this variation is acceptable (I'm trying to be less draconian about consistency when it isn't critical 😸), (2) it makes it super clear which side is the workaround which is nice, and (3) we have an active issue about preprocessor comment conventions anyways.
Let's ship this. 🚀
|
Thanks for making 64-bit atomics more efficient on x86! |
|
LLVM-46595 is fixed surprisingly quickly. Here's a commit: llvm/llvm-project@82206e7 So, the next step is probably waiting for the fixed version of LLVM to get into Visual Studio distribution? |
Yes. I've filed #1018 to track removal of workarounds. |
This ports MSVC-PR-269581, reverting microsoftGH-986 / MSVC-PR-240462. According to John Morgan: > We recently discovered a conflict between the 64-bit Interlocked > intrinsic functions newly implemented for x86 and the Windows 8.1 SDK. > To resolve the conflict we are reverting the change. We may later > implement an alternative solution to support these functions on x86.
This ports MSVC-PR-269581, reverting GH-986 / MSVC-PR-240462.
Resolves #965
Looks like red only diff change.unfortunately, did not succeed in it, clang does not have such intrinsics.Such changes are more likely to be helpful than green diff changes.