[AIE2P] Add alternative calling convention for library calls #664
Conversation
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
konstantinschwarz
requested review from
F-Stuckmann,
SagarMaheshwari99,
abhinay-anubola,
abnikant,
andcarminati,
katerynamuts,
khallouh,
martien-de-jong,
niwinanto and
stephenneuendorffer
as code owners
Collaborator
Author
|
This saves up to 512 bytes of stack (ArgMin/ArgMax), and some very minor code size savings. 
|
| setLibcallCallingConv(RTLIB::SREM_I32, CallingConv::AIE_PreserveAll_Vec); | ||
| setLibcallCallingConv(RTLIB::SREM_I64, CallingConv::AIE_PreserveAll_Vec); | ||
| setLibcallCallingConv(RTLIB::UREM_I32, CallingConv::AIE_PreserveAll_Vec); | ||
| setLibcallCallingConv(RTLIB::UREM_I64, CallingConv::AIE_PreserveAll_Vec); |
Collaborator
There was a problem hiding this comment.
I see some other libcalls in the LegalizerHelper. Are these only the verified ones?
Collaborator
Author
There was a problem hiding this comment.
Yes, these are only the ones I verified. Others could likely be included as well, but I wanted to keep this limited for now
In AIEs default calling convention, all vector registers are caller saved. However, most compiler-rt builtin library functions do not use vector registers. To avoid having to spill vectors to memory in the caller function, we can attach a different calling convention to these library functions.
F-Stuckmann
force-pushed
the
kschwarz.aie.altcc.libcalls
branch
from
9660c19 to
cebc746
Compare
F-Stuckmann
approved these changes
Nov 5, 2025
| : CalleeSavedRegs<(add lr, r8, r9, r10, r11, r12, r13, r14, r15, p6, p7)>; | ||
|
|
||
| def CSR_AIE2P_Vec | ||
| : CalleeSavedRegs<(add lr, r8, r9, r10, r11, r12, r13, r14, r15, p6, p7, |
Collaborator
There was a problem hiding this comment.
nit: can we write this as an extension to CSR_AIE2P?
Collaborator
There was a problem hiding this comment.
e.g. factoring using a named common set?
| : AIEBaseTargetLowering(TM, STI) { | ||
|
|
||
| if (VecCCLibcalls) { | ||
| setLibcallCallingConv(RTLIB::SINTTOFP_I32_F32, |
Collaborator
There was a problem hiding this comment.
nit: perhaps make a data-driven routine running on an array of function ids?
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 AIEs default calling convention, all vector registers are caller saved. However, most compiler-rt builtin library functions do not use vector registers. To avoid having to spill vectors to memory in the caller function, we can attach a different calling convention to these library functions.
I manually inspected each library function where we apply the alternative calling convention to make sure none of them actually use vector registers. To make this actually save and robust, we should also add a custom calling convention attribute to the frontend that ensures vector registers are actually saved by the callee.