https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #116 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Thiago Macieira from comment #115) > (In reply to Paul Floyd from comment #110) > > It’s everything. VEX isn’t my strong point, by my guess is that this would > > be one of the biggest changes to Valgrind for the last 15 years. > > To be clear, it's the EVEX prefix that is the problem. Valgrind has > supported VEX for a while. But since it hasn't supported EVEX, it has also > not added support for FP16, which is a massive addition to the instruction > set from two years ago. > > And then things are going to get worse with the VEX2 prefix for APX in a > couple of years. That is going to affect everything, not just the vector > code. Thiago, I really appreciate any help that you can offer. But PLEASE don't try to explain things like this to me. When I said VEX I meant VEX. That's this one here https://sourceware.org/git/?p=valgrind.git;a=tree;f=VEX;h=e080b4ada344869c7446d9bca8ab2aac832c2aaa;hb=HEAD Possibly "Valgrind Emulation", but not "Vector Extensions". It's the largest part of Valgrind that does all of the CPU emulation. -- You are receiving this mail because: You are watching all bug changes.
