You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Musl currently does not support the C11 standard for atomic variables, and as far as I know, it will never support it.
Unfortunately, plenty of applications depend on the respective header files to compile successfully.
As such, to avoid problems, one thing we could do is to implement stdatomic ourselves using gcc calls, as Unikraft is currently compiled with mostly gcc.
The text was updated successfully, but these errors were encountered:
I'm honestly confused, is there any technical reason why this can't be supported?
It doesn't make sense to go about making a standard libc implementation and not support C standard.
Musl currently does not support the C11 standard for atomic variables, and as far as I know, it will never support it.
Unfortunately, plenty of applications depend on the respective header files to compile successfully.
As such, to avoid problems, one thing we could do is to implement
stdatomic
ourselves using gcc calls, as Unikraft is currently compiled with mostly gcc.The text was updated successfully, but these errors were encountered: