https://bugs.kde.org/show_bug.cgi?id=323431
Anthony Romano <romanoanthony...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |romanoanthony...@gmail.com
--- Comment #8 from Anthony Romano <romanoanthony...@gmail.com> ---
Created attachment 121654
--> https://bugs.kde.org/attachment.cgi?id=121654&action=edit
support vpcmov
Hi, I've been hitting this one recently and it's in a lot of my system
libraries, so I added vpcmov support.
After I wrote this patch I poked around the bug tracker and realized I wrote a
broken XOP decoding patch for TBM bextr under a different account nearly six
years ago. It was ignored for a while and by the time it got any attention from
maintainers I had stopped relying on libvex internals for work. The bug was
later consolidated to another issue
(https://bugs.kde.org/show_bug.cgi?id=381819); there was modest traffic about 2
years ago, but I wasn't copied on it. Since there wasn't any progress at the
time, I changed my compiler settings to use bdver1 to avoid XOP TBM
instructions so it never came up again for me. My understanding is there's now
a VEX encoding for bextr.
The new attached patch piggybacks on PFX_VEX, introducing ESC_M8 instead of
incorrectly reusing the VEX ESC constants and adding PFX_XOP; it correctly
handles the pop case where XOP decoding should be abandoned. Adding the
alternative XOP bextr encoding from the other issue should be simple once
there's an XOP decode path.
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
