https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #115 from Thiago Macieira <thi...@kde.org> --- (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. -- You are receiving this mail because: You are watching all bug changes.
