Searched refs:AAPCS (Results 1 – 13 of 13) sorted by relevance
126 // ARM AAPCS (EABI) Calling Convention, common parts156 // ARM AAPCS (EABI) Calling Convention203 // ARM AAPCS-VFP (EABI) Calling Convention274 // AAPCS, and also preserves all floating point registers.304 // When enforcing an AAPCS compliant frame chain, R11 is used as the frame306 // This AAPCS alternative makes sure the frame index slots match the push
551 // If frame pointers are in use, they must follow the AAPCS definition, which558 "Create an AAPCS compliant frame chain">;
269 case ARMABIKind::AAPCS: in getABIDefaultCC()320 if (getABIKind() == ARMABIKind::AAPCS || in classifyHomogeneousAggregate()409 getABIKind() == ARMABIKind::AAPCS) { in classifyArgumentType()790 getABIKind() == ARMABIKind::AAPCS) { in EmitVAArg()
342 if (Kind != AArch64ABIKind::AAPCS) in classifyArgumentType()364 if (Kind == AArch64ABIKind::AAPCS) { in classifyArgumentType()
439 AAPCS = 0, enumerator460 AAPCS = 1, enumerator
145 AArch64ABIKind Kind = AArch64ABIKind::AAPCS; in createTargetCodeGenInfo()173 ARMABIKind Kind = ARMABIKind::AAPCS; in createTargetCodeGenInfo()
234 return (PCS->getPCS() == PcsAttr::AAPCS ? CC_AAPCS : CC_AAPCS_VFP); in getCallingConventionForDecl()
426 /// Whether to follow the AAPCS enforcing at least one read before storing to a volatile bitfield432 /// Whether to not follow the AAPCS that enforces volatile bit-field access width to be
2217 - If the function is AAPCS, Clang instructs the backend to realign the stack to2218 8 bytes on entry. This is a general requirement of the AAPCS at public2220 other AAPCS functions to be called.2222 itself is designed in such a way that functions obeying the normal AAPCS ABI5676 X8, X16-X19, SIMD and floating-point registers follow the AAPCS calling
2680 ["AAPCS", "AAPCS_VFP"]>];
42 // In AAPCS, an SRet is passed in X8, not X0 like a normal pointer parameter.677 // Darwin variants of AAPCS.706 // guarantees more than a normal AAPCS function. x16 and x17 are used on the
4715 PCS = PcsAttr::AAPCS; in handleCallConvAttr()
4911 …HelpText<"Follows the AAPCS standard that all volatile bit-field write generates at least one load…4918 " the AAPCS standard requirement stating that"