Lines Matching refs:opcode

111 SIMD opcodes. Instead attempting to execute any opcode will raise a "disabled
112 opcode" trap instead. If doing this it's recommended to pair it with
133 `for_each_op!` and `for_each_extended_op!` macros. Opcode numbers and opcode
141 come into play. The final Pulley opcode is reserved to indicate that an extended
142 opcode is being used. Extended opcodes follow this initial discriminator with a
143 16-bit integer which further indicates which extended opcode is being used. This
147 Pulley opcode assignment happens through the order of the `for_each_op!` macro
152 this means that there's a method-per-opcode and is how the interpreter is
158    [`Decode`] trait on each opcode. This is not literally modeled as but
162 2. A "tail loop" were each opcode handler is a Rust function. Control flow
200   to which Pulley opcode. Most of the time all the samples are just in the one
204   but it can be difficult to understand why a particular opcode was chosen.
206 It can sometimes be more beneficial to see time spent per Pulley opcode itself
208 instruction-level profiling in `perf` it can be useful to look at opcode-level
211 Pulley has limited support for opcode-level profiling. This is off-by-default as