Home
last modified time | relevance | path

Searched refs:AAPCS (Results 1 – 14 of 14) sorted by relevance

/openbsd-src/gnu/llvm/llvm/lib/Target/ARM/
H A DARMCallingConv.td126 // ARM AAPCS (EABI) Calling Convention, common parts
156 // ARM AAPCS (EABI) Calling Convention
203 // ARM AAPCS-VFP (EABI) Calling Convention
274 // AAPCS, and also preserves all floating point registers.
304 // When enforcing an AAPCS compliant frame chain, R11 is used as the frame
306 // This AAPCS alternative makes sure the frame index slots match the push
H A DARM.td556 "Create an AAPCS compliant frame chain">;
560 "Create an AAPCS compliant frame chain "
/openbsd-src/gnu/gcc/gcc/config/arm/
H A Dt-xscale-elf40 # supports generating them with the IWMMXT or AAPCS ABIs, neither of
/openbsd-src/gnu/llvm/llvm/docs/
H A DBigEndianNEON.rst100 AAPCS section in Considerations
103 The ARM procedure call standard (AAPCS) defines the ABI for passing vectors between functions in re…
147 | AAPCS | ``LDR`` | ``LD1 + REV`` |
H A DLangRef.rst443 - On iOS platforms, we use AAPCS-VFP calling convention.
/openbsd-src/gnu/llvm/llvm/lib/Target/AArch64/
H A DAArch64CallingConvention.td38 // In AAPCS, an SRet is passed in X8, not X0 like a normal pointer parameter.
497 // Darwin variants of AAPCS.
526 // guarantees more than a normal AAPCS function. x16 and x17 are used on the
/openbsd-src/gnu/llvm/clang/include/clang/Basic/
H A DCodeGenOptions.def476 /// Whether to follow the AAPCS enforcing at least one read before storing to a volatile bitfield
482 /// Whether to not follow the AAPCS that enforces volatile bit-field access width to be
H A DAttrDocs.td2118 - If the function is AAPCS, Clang instructs the backend to realign the stack to
2119 8 bytes on entry. This is a general requirement of the AAPCS at public
2121 other AAPCS functions to be called.
2123 itself is designed in such a way that functions obeying the normal AAPCS ABI
H A DAttr.td2377 ["AAPCS", "AAPCS_VFP"]>];
/openbsd-src/gnu/llvm/clang/lib/CodeGen/
H A DTargetInfo.cpp5501 AAPCS = 0, enumerator
5805 if (Kind != AArch64ABIInfo::AAPCS) in classifyArgumentType()
5828 if (Kind == AArch64ABIInfo::AAPCS) { in classifyArgumentType()
6311 AAPCS = 1, enumerator
6568 case AAPCS: return llvm::CallingConv::ARM_AAPCS; in getABIDefaultCC()
6616 if (getABIKind() == ARMABIInfo::AAPCS || in classifyHomogeneousAggregate()
6705 getABIKind() == ARMABIInfo::AAPCS) { in classifyArgumentType()
7090 getABIKind() == ARMABIInfo::AAPCS) { in EmitVAArg()
12231 AArch64ABIInfo::ABIKind Kind = AArch64ABIInfo::AAPCS; in getTargetCodeGenInfo()
12258 ARMABIInfo::ABIKind Kind = ARMABIInfo::AAPCS; in getTargetCodeGenInfo()
H A DCGCall.cpp229 return (PCS->getPCS() == PcsAttr::AAPCS ? CC_AAPCS : CC_AAPCS_VFP); in getCallingConventionForDecl()
/openbsd-src/gnu/llvm/clang/tools/libclang/
H A DCXType.cpp682 TCALLINGCONV(AAPCS); in clang_getFunctionTypeCallingConv()
/openbsd-src/gnu/llvm/clang/lib/Sema/
H A DSemaDeclAttr.cpp5075 PCS = PcsAttr::AAPCS; in handleCallConvAttr()
/openbsd-src/gnu/llvm/clang/include/clang/Driver/
H A DOptions.td3628 …HelpText<"Follows the AAPCS standard that all volatile bit-field write generates at least one load…
3633 BothFlags<[NoXarchOption, CC1Option], " the AAPCS standard requirement stating that"