Searched refs:epilogue (Results 1 – 8 of 8) sorted by relevance
| /Linux-v4.19/arch/x86/crypto/ |
| D | aes-x86_64-asm_64.S | 71 #define epilogue(FUNC,r1,r2,r5,r6,r7,r8,r9) \ macro
133 #define return(FUNC) epilogue(FUNC,R8,R2,R5,R6,R3,R4,R11)
|
| /Linux-v4.19/Documentation/bpf/ |
| D | bpf_design_QA.rst | 123 Q: Why BPF has implicit prologue and epilogue?
129 of LD_ABS insn). Those instructions need to invoke epilogue and
|
| /Linux-v4.19/arch/sh/kernel/cpu/sh5/ |
| D | switchto.S | 188 ! epilogue
|
| /Linux-v4.19/arch/arc/ |
| D | Kconfig | 172 * Function prologue/epilogue: ENTER_S, LEAVE_S
|
| /Linux-v4.19/Documentation/trace/ |
| D | ftrace-design.rst | 184 code. Since you are returning from a function (after the epilogue), you might
|
| /Linux-v4.19/arch/arm/crypto/ |
| D | sha1-armv4-large.S | 41 @ performance is affected by prologue and epilogue overhead,
|
| /Linux-v4.19/Documentation/s390/ |
| D | Debugging390.txt | 442 epilogue:
615 # Function epilogue below
664 # compiler adds 1 extra instruction to epilogue this is done to
|
| /Linux-v4.19/Documentation/networking/ |
| D | filter.txt | 790 Prologue and epilogue are emitted by JIT and are implicit in the
|
