Searched refs:AAPCS (Results 1 – 14 of 14) 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
559 "Create an AAPCS compliant frame chain">;563 "Create an AAPCS compliant frame chain "
271 case ARMABIKind::AAPCS: in getABIDefaultCC()322 if (getABIKind() == ARMABIKind::AAPCS || in classifyHomogeneousAggregate()411 getABIKind() == ARMABIKind::AAPCS) { in classifyArgumentType()795 getABIKind() == ARMABIKind::AAPCS) { in EmitVAArg()
326 if (Kind != AArch64ABIKind::AAPCS) in classifyArgumentType()348 if (Kind == AArch64ABIKind::AAPCS) { in classifyArgumentType()
416 AAPCS = 0, enumerator435 AAPCS = 1, enumerator
142 AArch64ABIKind Kind = AArch64ABIKind::AAPCS; in createTargetCodeGenInfo()166 ARMABIKind Kind = ARMABIKind::AAPCS; in createTargetCodeGenInfo()
230 return (PCS->getPCS() == PcsAttr::AAPCS ? CC_AAPCS : CC_AAPCS_VFP); in getCallingConventionForDecl()
23 in a manner similar to that specified by AAPCS:
416 /// Whether to follow the AAPCS enforcing at least one read before storing to a volatile bitfield422 /// Whether to not follow the AAPCS that enforces volatile bit-field access width to be
2174 - If the function is AAPCS, Clang instructs the backend to realign the stack to2175 8 bytes on entry. This is a general requirement of the AAPCS at public2177 other AAPCS functions to be called.2179 itself is designed in such a way that functions obeying the normal AAPCS ABI
2520 ["AAPCS", "AAPCS_VFP"]>];
37 // In AAPCS, an SRet is passed in X8, not X0 like a normal pointer parameter.620 // Darwin variants of AAPCS.649 // guarantees more than a normal AAPCS function. x16 and x17 are used on the
5205 PCS = PcsAttr::AAPCS; in handleCallConvAttr()
4661 …HelpText<"Follows the AAPCS standard that all volatile bit-field write generates at least one load…4668 " the AAPCS standard requirement stating that"