summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorQuentin Colombet <qcolombet@apple.com>2019-11-06 11:09:12 -0800
committerQuentin Colombet <qcolombet@apple.com>2019-11-06 11:27:50 -0800
commit52af7aedfe5dd5cfb1a6f486040a2549bbdbcf93 (patch)
treeb3b0b5b8e4a2e777daf08865bea20ef6598e1fa4 /lldb/packages/Python/lldbsuite/test/python_api
parent6da58e7e0fac1e421d6a5a6e48ed8836c67ac543 (diff)
downloadbcm5719-llvm-52af7aedfe5dd5cfb1a6f486040a2549bbdbcf93.tar.gz
bcm5719-llvm-52af7aedfe5dd5cfb1a6f486040a2549bbdbcf93.zip
[GISel][ArtifactCombiner] Relax the constraint to combine unmerge with concat_vectors
The combine G_UNMERGE_VALUES with G_CONCAT_VECTORS used to only be performed when the result type of the G_UNMERGE_VALUES was a vector type. In other words, we were expecting that the G_UNMERGE_VALUES was effectively the exact opposite of the G_CONCAT_VECTORS. Lift that constraint by allowing any G_UNMERGE_VALUES to be combined with any G_CONCAT_VECTORS (as long as the size of the different pieces that we merge/unmerge match). Differential Revision: https://reviews.llvm.org/D69288
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud