Searched full:aapcs (Results 1 – 12 of 12) sorted by relevance
12 * A compiler-generated thunk calls this with a non-AAPCS calling32 * To call a regular AAPCS function we must save x2 to x15 (which we can
14 * Register x18 is designated as the 'platform' register by the AAPCS,
25 * Each instrumented function follows the AAPCS, so here x0-x8 and x18-x30 are116 * x19-x29 per the AAPCS, and we created frame records upon entry, so we need
59 * when applying stack alignment constraints: the AAPCS mandates a in invoke_syscall()
371 * All instrumented functions follow the AAPCS, so x0-x8 and x19-x30 are live,386 * being traced, the MOV is not harmful given x9 is not live per the AAPCS.
23 in a manner similar to that specified by AAPCS:
49 VDSO_CAFLAGS += -mabi=aapcs-linux -mfloat-abi=soft
90 CFLAGS += -march=armv7-a -mabi=aapcs-linux102 CFLAGS += -march=armv7-a -mabi=aapcs-linux
113 CFLAGS_ABI :=-mabi=aapcs-linux -mfpu=vfp
124 * Internal, non-AAPCS compliant functions that implement the core AES
264 @ Invoke the v7_invalidate_l1() function, which adheres to the AAPCS
506 /* Save FP and LR registers to stay align with ARM64 AAPCS */ in build_prologue()