diff options
| author | Craig Topper <craig.topper@intel.com> | 2018-02-03 23:00:31 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2018-02-03 23:00:31 +0000 |
| commit | fc5bd023dd9654c09267c287c3d26ddceeaf4161 (patch) | |
| tree | b9f28001996204e614fa786e5b72c7875487af92 /libcxx/test/std | |
| parent | 7aec5063a5b99ca67614352ff2f25942baf49ceb (diff) | |
| download | bcm5719-llvm-fc5bd023dd9654c09267c287c3d26ddceeaf4161.tar.gz bcm5719-llvm-fc5bd023dd9654c09267c287c3d26ddceeaf4161.zip | |
[DAGCombiner] When folding fold (sext/zext (and/or/xor (sextload/zextload x), cst)) -> (and/or/xor (sextload/zextload x), (sext/zext cst)) make sure we check the legality of the full extended load.
Summary:
If the load is already an extended load we should be using the memory VT for the legality check, not just the VT of the current extension.
I don't have a test case, just noticed it while investigating some load extension improvements.
Reviewers: RKSimon, spatel, niravd
Reviewed By: niravd
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D42783
llvm-svn: 324181
Diffstat (limited to 'libcxx/test/std')
0 files changed, 0 insertions, 0 deletions

