Matt Arsenault
2015-Apr-20 20:33 UTC
[LLVMdev] Why are imm shifts where imm >= width type eliminated entirely?
On 04/20/2015 01:25 PM, David Majnemer wrote:> These optimizations are not always run on IR that is fed to the backend.The DAG combiner also performs the undefined shift -> undef though, so it should still be OK -Matt
Tim Northover
2015-Apr-20 20:44 UTC
[LLVMdev] Why are imm shifts where imm >= width type eliminated entirely?
> The DAG combiner also performs the undefined shift -> undef though, so it > should still be OKDAG combiner doesn't really run to convergence as far as I'm aware, so you often get extremely difficult to test but necessary checks like this. Tim.
Matthias Braun
2015-Apr-21 04:21 UTC
[LLVMdev] Why are imm shifts where imm >= width type eliminated entirely?
There can also be other “problems" like this one: http://reviews.llvm.org/D6946 <http://reviews.llvm.org/D6946> - Matthias> On Apr 20, 2015, at 1:44 PM, Tim Northover <t.p.northover at gmail.com> wrote: > >> The DAG combiner also performs the undefined shift -> undef though, so it >> should still be OK > > DAG combiner doesn't really run to convergence as far as I'm aware, so > you often get extremely difficult to test but necessary checks like > this. > > Tim. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150420/483bba97/attachment.html>
Seemingly Similar Threads
- [LLVMdev] Why are imm shifts where imm >= width type eliminated entirely?
- [LLVMdev] Why are imm shifts where imm >= width type eliminated entirely?
- [LLVMdev] Why are imm shifts where imm >= width type eliminated entirely?
- New register class and patterns
- BPF backend with vector operations - error "Could not infer all types in, pattern!"