projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7fff9a9) | patch
[LegalizeVectorOps] After custom legalizing an extending load or a truncating store...
authorCraig Topper <craig.topper@intel.com>
Fri, 16 Nov 2018 21:04:58 +0000 (21:04 +0000)
committerCraig Topper <craig.topper@intel.com>
Fri, 16 Nov 2018 21:04:58 +0000 (21:04 +0000)
commit9e97054211a898b9670979512e9e0b227d72bec3
treeeac0960575edec527eb2a059258a543b1e2bcdd2tree | snapshot
parent7fff9a9aef4849be8f7b1a8949b12a22905f6c1dcommit | diff
[LegalizeVectorOps] After custom legalizing an extending load or a truncating store, make sure the custom code is also legal.

For example, on X86 we emit a sign_extend_vector_inreg from LowerLoad and without sse4.1 this node will need further legalization. Previously this sign_extend_vector_inreg was being custom lowered during DAG legalization instead of vector op legalization.

Unfortunately, this doesn't seem to matter for the output of any existing lit tests.

llvm-svn: 347094
llvm/lib/CodeGen/SelectionDAG/LegalizeVectorOps.cpp diff | blob | history
Domain: System / Toolchain;