bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	[PatternMatch, InstSimplify] enhance m_AllOnes() to ignore undef elements in ↵	Sanjay Patel	2018-02-18	1	-2/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	vectors Loosening the matcher definition reveals a subtle bug in InstSimplify (we should not assume that because an operand constant matches that it's safe to return it as a result). So I'm making that change here too (that diff could be independent, but I'm not sure how to reveal it before the matcher change). This also seems like a good reason to not include matchers that capture the value. We don't want to encourage the potential misstep of propagating undef values when it's not allowed/intended. I didn't include the capture variant option here or in the related rL325437 (m_One), but it already exists for other constant matchers. llvm-svn: 325466
*	[InstSimplify] add tests with vector undef elts; NFC	Sanjay Patel	2018-02-18	1	-7/+9
\| \| \| \|	llvm-svn: 325465
*	[InstSimplify] Use m_APInt instead of m_ConstantInt in ((V + N) & C1) \| (V & ↵	Craig Topper	2017-05-26	1	-1/+40
\| \| \| \| \| \| \| \| \| \|	C2) handling in order to support splat vectors. The tests here are have operands commuted to provide more coverage. I also commuted one of the instructions in the scalar tests so the 4 tests cover the 4 commuted variations Differential Revision: https://reviews.llvm.org/D33599 llvm-svn: 304021
*	[InstSimplify, InstCombine] move 'or' simplification tests; NFC	Sanjay Patel	2017-05-10	1	-0/+181
	Surprisingly, I don't think these are redundant for InstSimplify. They were just misplaced as InstCombine tests. llvm-svn: 302684