Searched refs:zext (Results 1 – 9 of 9) sorted by relevance
| /linux-6.12.1/arch/csky/abiv2/ |
| D | memset.S | 28 zext r18, r2, 31, 4
43 zext r18, r2, 3, 2
54 zext r18, r2, 2, 0
|
| D | memcpy.S | 22 zext r18, r2, 31, 4
57 zext r18, r2, 3, 2
69 zext r18, r2, 1, 0
|
| D | memmove.S | 28 zext r18, r2, 31, 4
61 zext r18, r2, 3, 2
73 zext r18, r2, 1, 0
|
| D | memcmp.S | 24 zext r18, r2, 31, 4
58 zext r18, r2, 3, 2
71 zext r18, r2, 1, 0
|
| /linux-6.12.1/arch/loongarch/net/ |
| D | bpf_jit.h | 119 goto zext; in move_imm()
125 goto zext; in move_imm()
165 zext: in move_imm()
|
| /linux-6.12.1/Documentation/bpf/ |
| D | bpf_design_QA.rst | 180 is required, and insert an explicit zero-extension (zext) instruction
181 (a mov32 variant). This means that for architectures without zext hardware
186 enable zext insertion in the verifier).
189 support for zext. In that case, if verifier zext insertion is enabled,
190 it could lead to the insertion of unnecessary zext instructions. Such
192 back-end: if one instruction has hardware support for zext and if the next
193 instruction is an explicit zext, then the latter can be skipped when doing
|
| /linux-6.12.1/arch/arc/net/ |
| D | bpf_jit.h | 42 u8 zext(u8 *buf, u8 rd);
|
| D | bpf_jit_arcv2.c | 1305 u8 zext(u8 *buf, u8 rd) in zext() function
2220 len += zext(BUF(buf, len), rd); in gen_swap()
2251 len += zext(BUF(buf, len), rd); in gen_swap()
|
| D | bpf_jit_core.c | 1044 len += zext(BUF(buf, len), dst); in handle_insn()
|