Skip to content

[compiler-rt] Don't build SME routines if __arm_cpu_features is not initialised. #119703

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

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

sdesmalen-arm
Copy link
Collaborator

According to the conversation
here, some platforms don't enable __arm_cpu_features with a global constructor, but rather do so lazily when called from the FMV resolver.

PR #119414 removed the CMake guard to check to see if the targetted platform is baremetal or supports sys/auxv. Without this check, the routines rely on __arm_cpu_features being initialised when they may not be, depending on the platform.

This PR simply avoids building the SME routines for those platforms for now.

…nitialised.

According to the conversation
[here](llvm#119414 (comment)),
some platforms don't enable `__arm_cpu_features` with a global constructor,
but rather do so lazily when called from the FMV resolver.

PR llvm#119414 removed the CMake guard to check to see if the targetted
platform is baremetal or supports sys/auxv. Without this check, the
routines rely on `__arm_cpu_features` being initialised when they
may not be, depending on the platform.

This PR simply avoids building the SME routines for those platforms for now.
@sdesmalen-arm sdesmalen-arm merged commit e5371ed into llvm:main Dec 12, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants