diff options
author | Sanjay Patel <spatel@rotateright.com> | 2019-07-25 12:14:27 +0000 |
---|---|---|
committer | Sanjay Patel <spatel@rotateright.com> | 2019-07-25 12:14:27 +0000 |
commit | bc4a63fd3c29c1a8ce22891bf34ee4dccfef578c (patch) | |
tree | dec720d60f4a9d6f8ca4397cb1c11b10cf09b2ce /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp | |
parent | 4e1d188be2868aef71f8603f28ca4703723cb97a (diff) | |
download | bcm5719-llvm-bc4a63fd3c29c1a8ce22891bf34ee4dccfef578c.tar.gz bcm5719-llvm-bc4a63fd3c29c1a8ce22891bf34ee4dccfef578c.zip |
[InstCombine] try to narrow a truncated load
trunc (load X) --> load (bitcast X to narrow type)
We have this transform in DAGCombiner::ReduceLoadWidth(), but the truncated
load pattern can interfere with other instcombine transforms, so I'd like to
allow the fold sooner.
Example:
https://bugs.llvm.org/show_bug.cgi?id=16739
...in that report, we have bitcasts bracketing these ops, so those could get
eliminated too.
We've generally ruled out widening of loads early in IR ( LoadCombine -
http://lists.llvm.org/pipermail/llvm-dev/2016-September/105291.html ), but
that reasoning may not apply to narrowing if we can preserve information
such as the dereferenceable range.
Differential Revision: https://reviews.llvm.org/D64432
llvm-svn: 367011
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions