[X86] After turning VSELECT into SHRUNKBLEND, make we push the VSELECT into the workl...
authorCraig Topper <craig.topper@intel.com>
Thu, 10 Jan 2019 00:14:27 +0000 (00:14 +0000)
committerCraig Topper <craig.topper@intel.com>
Thu, 10 Jan 2019 00:14:27 +0000 (00:14 +0000)
commitc38c9c120f3583eed698f5c0e3e21b4c03f6ad61
treefd01fdcb2b3120b8a7b37246d0b26ff82fbc8b58
parent2f72a7521a59b3e292c342d0470ef5a6044be99a
[X86] After turning VSELECT into SHRUNKBLEND, make we push the VSELECT into the worklist so it can be deleted.

Found while trying to figure out why my second version of D56421 worked better than the first version. We weren't deleting the vselect in a timely fashion and that caused SimplfyDemandedBit to see an additional user.

The new version doesn't have this problem so this fix isn't needed there, but seemed like the right thing to do.

llvm-svn: 350781
llvm/lib/Target/X86/X86ISelLowering.cpp