-
Notifications
You must be signed in to change notification settings - Fork 84
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
Build error on Windows ARM #763
Comments
the relevant code: static __forceinline unsigned __int64 _re_atomic_load(
size_t size, const void *a)
{
unsigned __int64 v;
assert(size == 1u || size == 2u || size == 4u || size == 8u);
_ReadWriteBarrier();
switch (size) {
case 1u:
v = __iso_volatile_load8((const unsigned __int8*)a);
break;
case 2u:
v = __iso_volatile_load16((const unsigned __int16*)a);
break;
case 4u:
v = __iso_volatile_load32((const unsigned __int32*)a);
break;
default:
v = __iso_volatile_load64((const unsigned __int64*)a);
break;
}
_ReadWriteBarrier();
if (mo != re_memory_order_relaxed && mo <= re_memory_order_acquire) // <---!
__dmb(0x0b); /* dmb ish */
_ReadWriteBarrier();
return v;
} what is "mo" ? |
Stands for memory order (arg is missing), is mostly unneeded for load, but arm is a special case I think. @Lastique can you have a look. |
Lastique
added a commit
to Lastique/re
that referenced
this issue
Apr 15, 2023
Yes, this is supposed to be a memory order argument. Please, check if #766 fixes this. |
sreimers
pushed a commit
that referenced
this issue
Apr 15, 2023
KORuL
pushed a commit
to KORuL/re
that referenced
this issue
May 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Configure:
Build:
The text was updated successfully, but these errors were encountered: