summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2018-04-09 20:37:14 +0000
committerCraig Topper <craig.topper@intel.com>2018-04-09 20:37:14 +0000
commit47b2f9d836f8fbde3c70df18742270b36f5fe55d (patch)
tree53de14fda8069de9fad6c8bba58943ba1d680625 /lldb/source/Plugins/ScriptInterpreter/Python
parent6662e9890b0eb7b3eea19dcb4153c0ea59c1103c (diff)
downloadbcm5719-llvm-47b2f9d836f8fbde3c70df18742270b36f5fe55d.tar.gz
bcm5719-llvm-47b2f9d836f8fbde3c70df18742270b36f5fe55d.zip
[X86] Don't use Lower512IntUnary to split bitcasts with v32i16/v64i8 types on targets without AVX512BW.
LowerIntUnary as its name says has an assert for integer types. But for the bitcast case one side might be an FP type. Rather than making sure the function really works for fp types and renaming it. Just do really basic splitting directly. The LowerIntUnary has the advantage that it can peek through BUILD_VECTOR because every other call is during Lowering. But these calls are during legalization and will be followed by a DAG combine round. Revert some change to LowerVectorIntUnary that were originally made just to make these two calls work even in pure integer cases. This was found purely by compiling the avx512f-builtins.c test from clang so I've copied over the offending function from that. llvm-svn: 329616
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud