Indeed, my bad, i was thinking about the "trivial patch" submission process.
For reference, the submitted patch can be found here
https://lists.nongnu.org/archive/html/qemu-devel/2022-01/msg00822.html
Thanks,
Stevie
On Thu, Jan 6, 2022 at 5:29 PM Richard Henderson <
richard.hender...@linaro.org>
On 1/6/22 1:14 AM, Stevie Lavern wrote:
Do you think it qualifies as "trivial patch" or should i go on with the full patch
submission process?
There is no "short" patch submission process.
r~
Hello,
Thanks for you answer!
I may put together a patch to crash if VEX.L is 1 (shouldn't be hard) and
submit it to the patch list.
Do you think it qualifies as "trivial patch" or should i go on with the
full patch submission process?
On Thu, Jan 6, 2022 at 3:45 AM Richard Henderson <
richard.h
On 1/5/22 9:09 AM, Stevie Lavern wrote:
Hello,
I'm currently testing various binaries under qemu linux user and went into a
strange bug.
Here is the TLDR: is there a reason to allow VEX.L to be 1 when not supporting AVX
instructions?
There are some integer instructions that use vex encoding,
Hello,
I'm currently testing various binaries under qemu linux user and went into
a strange bug.
Here is the TLDR: is there a reason to allow VEX.L to be 1 when not
supporting AVX instructions? Crashing with illegal op may save some time
and headache to users.
And now for some context:
One of my
