summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-08-20 06:58:00 +0000
committerCraig Topper <craig.topper@intel.com>2019-08-20 06:58:00 +0000
commit1ada137854be55265f1b8128e1a19c57c48582f9 (patch)
tree04fa0ffa08c6063e3497cc5b49cd7dbfe80b2ff1 /lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c
parent12cbbab9d9366d37bb2c6f1057491d07c83aba59 (diff)
downloadbcm5719-llvm-1ada137854be55265f1b8128e1a19c57c48582f9.tar.gz
bcm5719-llvm-1ada137854be55265f1b8128e1a19c57c48582f9.zip
[X86] Add back the -x86-experimental-vector-widening-legalization comand line flag and all associated code, but leave it enabled by default
Google is reporting performance issues with the new default behavior and have asked for a way to switch back to the old behavior while we investigate and make fixes. I've restored all of the code that had since been removed and added additional checks of the command flag onto code paths that are not otherwise guarded by a check of getTypeAction. I've also modified the cost model tables to hopefully get us back to the previous costs. Hopefully we won't need to support this for very long since we have no test coverage of the old behavior so we can very easily break it. llvm-svn: 369332
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud