Searched refs:AAPCS (Results 1 – 13 of 13) sorted by relevance
275 case ARMABIKind::AAPCS: in getABIDefaultCC()328 if (getABIKind() == ARMABIKind::AAPCS || in classifyHomogeneousAggregate()453 getABIKind() == ARMABIKind::AAPCS) { in classifyArgumentType()830 getABIKind() == ARMABIKind::AAPCS) { in EmitVAArg()
452 if (Kind != AArch64ABIKind::AAPCS) in classifyArgumentType()468 if (Kind == AArch64ABIKind::AAPCS) { in classifyArgumentType()480 if (Kind == AArch64ABIKind::AAPCS) { in classifyArgumentType()579 if (Kind == AArch64ABIKind::AAPCS) { in classifyReturnType()700 if (Kind == AArch64ABIKind::AAPCS && Ty->isSVESizelessBuiltinType()) { in passAsAggregateType()
126 // ARM AAPCS (EABI) Calling Convention, common parts157 // ARM AAPCS (EABI) Calling Convention204 // ARM AAPCS-VFP (EABI) Calling Convention296 // AAPCS, and also preserves all floating point registers.
561 // If frame pointers are in use, they must follow the AAPCS definition, which568 "Create an AAPCS compliant frame chain">;
482 AAPCS = 0, enumerator503 AAPCS = 1, enumerator
143 AArch64ABIKind Kind = AArch64ABIKind::AAPCS; in createTargetCodeGenInfo()171 ARMABIKind Kind = ARMABIKind::AAPCS; in createTargetCodeGenInfo()
277 return (PCS->getPCS() == PcsAttr::AAPCS ? CC_AAPCS : CC_AAPCS_VFP); in getCallingConventionForDecl()
48 // In AAPCS, an SRet is passed in X8, not X0 like a normal pointer parameter.713 // Darwin variants of AAPCS.742 // guarantees more than a normal AAPCS function. x16 and x17 are used on the
433 /// Whether to follow the AAPCS enforcing at least one read before storing to a volatile bitfield442 /// Whether to not follow the AAPCS that enforces volatile bit-field access width to be
2666 - If the function is AAPCS, Clang instructs the backend to realign the stack to2667 8 bytes on entry. This is a general requirement of the AAPCS at public2669 other AAPCS functions to be called.2671 itself is designed in such a way that functions obeying the normal AAPCS ABI6449 X8, X16-X19, SIMD and floating-point registers follow the AAPCS calling
2972 ["AAPCS", "AAPCS_VFP"]>];
5317 PCS = PcsAttr::AAPCS; in handleCallConvAttr()
5187 …HelpText<"Follows the AAPCS standard that all volatile bit-field write generates at least one load…5194 " the AAPCS standard requirement stating that"