| /openbmc/qemu/docs/ |
| H A D | defs.rst.inc | 3 all rST files as part of the epilogue by docs/conf.py. conf.py
|
| /openbmc/qemu/target/arm/ |
| H A D | syndrome.h | 347 bool epilogue, bool wrong_option, bool option_a, in syn_mop() argument
352 (epilogue << 18) | (wrong_option << 17) | (option_a << 16) | in syn_mop()
|
| /openbmc/qemu/hw/arm/ |
| H A D | smmuv3.c | 865 goto epilogue; in smmuv3_translate()
871 goto epilogue; in smmuv3_translate()
876 goto epilogue; in smmuv3_translate()
881 goto epilogue; in smmuv3_translate()
894 goto epilogue; in smmuv3_translate()
930 goto epilogue; in smmuv3_translate()
984 epilogue: in smmuv3_translate()
|
| /openbmc/qemu/docs/devel/ |
| H A D | tcg.rst | 41 current TB, going through the TB epilogue, and then back to the
63 code address is returned, otherwise the address of the JIT epilogue is
|
| H A D | tcg-ops.rst | 676 jump to the TCG epilogue to go back to the exec loop.
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 59 functions use specific prologue and epilogue sequences. Architectures
138 epilogue a frame pointer may be transiently invalid, or during the function
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | bpf_design_QA.rst | 143 Q: Why BPF has implicit prologue and epilogue?
149 of LD_ABS insn). Those instructions need to invoke epilogue and
|
| H A D | classic_vs_extended.rst | 187 Prologue and epilogue are emitted by JIT and are implicit in the
|
| /openbmc/qemu/tcg/mips/ |
| H A D | tcg-target.c.inc | 1689 /* jmp to the given host address (could be epilogue) */
2402 /* Generate global QEMU prologue and epilogue code */
2441 * and fall through to the rest of the epilogue.
2446 /* TB epilogue */
|
| /openbmc/linux/arch/arc/ |
| H A D | Kconfig | 145 * Function prologue/epilogue: ENTER_S, LEAVE_S
|
| /openbmc/linux/Documentation/trace/ |
| H A D | ftrace-design.rst | 184 code. Since you are returning from a function (after the epilogue), you might
|
| /openbmc/linux/arch/arm/crypto/ |
| H A D | sha1-armv4-large.S | 41 @ performance is affected by prologue and epilogue overhead,
|
| /openbmc/qemu/target/arm/tcg/ |
| H A D | a64.decode | 560 # SETE (epilogue), and each of those has different flavours to
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gcc/gcc/ |
| H A D | CVE-2023-4039.patch | 74 /* When shadow call stack is enabled, the scs_pop in the epilogue will
784 If a frame pointer is not needed, the epilogue adds final_adjust
789 Therefore, if the epilogue needs to restore the stack pointer from
1059 /* When shadow call stack is enabled, the scs_pop in the epilogue will
2528 + (including callees and allocas) that happens before the epilogue is
|
| /openbmc/qemu/tcg/tci/ |
| H A D | tcg-target.c.inc | 953 /* Generate global QEMU prologue and epilogue code. */
|
| /openbmc/qemu/tcg/riscv/ |
| H A D | tcg-target.c.inc | 2069 /* Generate global QEMU prologue and epilogue code */
2096 /* TB epilogue */
|
| /openbmc/qemu/tcg/i386/ |
| H A D | tcg-target.c.inc | 2458 /* jmp to the given host address (could be epilogue) */
4124 /* Generate global QEMU prologue and epilogue code */
4173 * and fall through to the rest of the epilogue.
4178 /* TB epilogue */
|
| /openbmc/qemu/tcg/loongarch64/ |
| H A D | tcg-target.c.inc | 2274 /* Generate global QEMU prologue and epilogue code */
2301 /* TB epilogue */
|
| /openbmc/linux/net/ceph/ |
| H A D | messenger_v2.c | 1008 void *epilogue, struct page **pages, int dpos, in setup_message_sgs() argument
1059 sg_set_buf(cur_sg, epilogue, in setup_message_sgs()
|
| /openbmc/qemu/tcg/aarch64/ |
| H A D | tcg-target.c.inc | 3135 * and fall through to the rest of the epilogue.
3141 /* TB epilogue */
|
| /openbmc/qemu/tcg/sparc64/ |
| H A D | tcg-target.c.inc | 923 /* Generate global QEMU prologue and epilogue code */
|
| /openbmc/qemu/tcg/s390x/ |
| H A D | tcg-target.c.inc | 3467 * and fall through to the rest of the epilogue.
3472 /* TB epilogue */
|
| /openbmc/qemu/tcg/arm/ |
| H A D | tcg-target.c.inc | 2939 * and fall through to the rest of the epilogue.
|