https://bugs.kde.org/show_bug.cgi?id=409501
Julian Seward changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=409501
--- Comment #6 from 4ctrl.alt@gmail.com ---
That makes sense thanks. It looks like XOP was abandoned by AMD with Zen which
probably makes it even less of a priority.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409501
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #5 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=409501
--- Comment #4 from 4ctrl.alt@gmail.com ---
I'm confused why valgrind version 3.14 released in October of 2018 does not
recognize an XOP instruction that AMD announced in May of 2008.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=409501
--- Comment #3 from Mark Wielaard ---
vpcomw is part of the AMD XOP instruction set:
https://en.wikipedia.org/wiki/XOP_instruction_set
gcc -march=bdver1 enables this instruction set (among others):
bdver1
CPUs based on AMD
https://bugs.kde.org/show_bug.cgi?id=409501
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=409501
--- Comment #1 from 4ctrl.alt@gmail.com ---
It seems to be executing code in the qtcore library. This library was compiled
with the following relevant flags from my systems configuration:
"-O2 -march=bdver1 -pipe"
I'm guessing the -march flag is
