aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2020-06-25 10:08:03 -0700
committerCraig Topper <craig.topper@intel.com>2020-06-25 11:25:35 -0700
commit636d31a5c341ff2ca5eefd6075ff059eb60b5a80 (patch)
treeefc861733bdbbe4e290aed313b223aeec6bbf942 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
parent821271ea27e312cd3252457a1bac891bc36880b9 (diff)
downloadllvm-636d31a5c341ff2ca5eefd6075ff059eb60b5a80.zip
llvm-636d31a5c341ff2ca5eefd6075ff059eb60b5a80.tar.gz
llvm-636d31a5c341ff2ca5eefd6075ff059eb60b5a80.tar.bz2
[X86] Don't imply -mprfchw when -m3dnow is specified. Enable prefetchw in the backend with 3dnow feature.
The PREFETCHW instruction was originally part of the 3DNow. But it was given its own CPUID bit on later CPUs just before 3DNow was deprecated. We were setting the -mprfchw flag if -m3dnow was passed or the CPU supported 3dnow unless -mno-prfchw was passed. But -march=native on a CPU without the PRFCHW CPUID bit set will pass -mno-prfchw. So -march=k8 will behave differently than -march=native on a K8 for example. So remove this implicit setting from the frontend and instead enable the backend to use PREFETCHW if 3dnow OR prfchw is enabled. Also enable PRFCHW flag on amdfam10/barcelona which seems to be where this CPUID bit was introduced. That CPU also supported 3dnow.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions