[libc] Add support for MVE to Arm startup code#167338
Merged
Conversation
Member
|
@llvm/pr-subscribers-libc Author: Victor Campos (vhscampos) ChangesIn order to have MVE support, the same bits of the CPACR register that enable the floating-point extension must be set. Full diff: https://github.com/llvm/llvm-project/pull/167338.diff 1 Files Affected:
diff --git a/libc/startup/baremetal/arm/start.cpp b/libc/startup/baremetal/arm/start.cpp
index 4740067722022..b22529f214216 100644
--- a/libc/startup/baremetal/arm/start.cpp
+++ b/libc/startup/baremetal/arm/start.cpp
@@ -131,20 +131,23 @@ namespace LIBC_NAMESPACE_DECL {
__arm_wsr("CPSR_c", 0x13); // SVC
#endif
-#ifdef __ARM_FP
-// Enable FPU
-#if __ARM_ARCH_PROFILE == 'M'
+#if __ARM_ARCH_PROFILE == 'M' && \
+ (defined(__ARM_FP) || defined(__ARM_FEATURE_MVE))
+ // Enable FPU and MVE. They can't be enabled independently: the two are
+ // governed by the same bits in CPACR.
// Based on
// https://developer.arm.com/documentation/dui0646/c/Cortex-M7-Peripherals/Floating-Point-Unit/Enabling-the-FPU
- // Set CPACR cp10 and cp11
+ // Set CPACR cp10 and cp11.
auto cpacr = (volatile uint32_t *const)0xE000ED88;
*cpacr |= (0xF << 20);
__dsb(0xF);
__isb(0xF);
-#elif __ARM_ARCH_PROFILE == 'A' || __ARM_ARCH_PROFILE == 'R'
+#elif (__ARM_ARCH_PROFILE == 'A' || __ARM_ARCH_PROFILE == 'R') && \
+ defined(__ARM_FP)
+ // Enable FPU.
// Based on
// https://developer.arm.com/documentation/dui0472/m/Compiler-Coding-Practices/Enabling-NEON-and-FPU-for-bare-metal
- // Set CPACR cp10 and cp11
+ // Set CPACR cp10 and cp11.
uint32_t cpacr = __arm_rsr("p15:0:c1:c0:2");
cpacr |= (0xF << 20);
__arm_wsr("p15:0:c1:c0:2", cpacr);
@@ -154,7 +157,6 @@ namespace LIBC_NAMESPACE_DECL {
__asm__ __volatile__("vmrs %0, FPEXC" : "=r"(fpexc) : :);
fpexc |= (1 << 30);
__asm__ __volatile__("vmsr FPEXC, %0" : : "r"(fpexc) :);
-#endif
#endif
// Perform the equivalent of scatterloading
|
lntue
reviewed
Nov 11, 2025
statham-arm
reviewed
Nov 11, 2025
Collaborator
statham-arm
left a comment
There was a problem hiding this comment.
In MVE, it's also important to initialize the LTPSIZE field in FPSCR, because on at least some platforms it starts off at 0, but 0 means tail predication is currently active. I think it would be a good idea to set it to 4 ("no tail predication") at startup, if there's a piece of code that knows it's enabling MVE at all.
In order to have MVE support, the same bits of the CPACR register that enable the floating-point extension must be set.
3ca0f6b to
77b94bd
Compare
statham-arm
approved these changes
Nov 12, 2025
Collaborator
statham-arm
left a comment
There was a problem hiding this comment.
I have one remaining comment nit, but otherwise LGTM.
git-crd
pushed a commit
to git-crd/crd-llvm-project
that referenced
this pull request
Nov 13, 2025
In order to have MVE support, the same bits of the CPACR register that enable the floating-point extension must be set.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In order to have MVE support, the same bits of the CPACR register that enable the floating-point extension must be set.