https://bugs.kde.org/show_bug.cgi?id=374596
--- Comment #12 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Tom Hughes from comment #11) > No that's not the problem at all. Yes we may sometimes advertise different > flags from the real CPU but the issue here is that we advertise that we > don't support an instruction Do we ? See below extract from comment 1: > Strangely (due to VEX simulating a different CPU stepping) if we comment out > the code that executes RDTCSP, the program under valgrind then reports the > instruction as being supported. So, I am wondering what Valgrind really detects and reports. Maybe there is something strange there (as in my case, even if my strange case is avx2 related, not rdtscp related : for me, it reports an avx2 flag, but calls a non avx2 dirty helper. -- You are receiving this mail because: You are watching all bug changes.
