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
I've just came across this post the other day which suggests that even though the feature registers cannot be accessed in EL0, the kernel puts this info in the auxiliary vector which is the recommended way to do feature detection on ARM and AArch64 without string parsing.
If you are willing to hard code the enum values when glibc header does not provide them, you can also use dlsym to find this symbol in case an old glibc is used at compile time (this would be useful for julia since the arm binary is going to be compiled on a host with an old glibc).
The text was updated successfully, but these errors were encountered:
I've just came across this post the other day which suggests that even though the feature registers cannot be accessed in EL0, the kernel puts this info in the auxiliary vector which is the recommended way to do feature detection on ARM and AArch64 without string parsing.
If you are willing to hard code the enum values when glibc header does not provide them, you can also use
dlsym
to find this symbol in case an old glibc is used at compile time (this would be useful for julia since the arm binary is going to be compiled on a host with an old glibc).The text was updated successfully, but these errors were encountered: