aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineFunction.cpp
diff options
context:
space:
mode:
authorAnna Thomas <anna@azul.com>2020-03-06 11:07:11 -0500
committerAnna Thomas <anna@azul.com>2020-03-06 16:28:49 -0500
commit59029b9eef23c72d904f9a6b182c5cd4402a69c5 (patch)
tree6c0c2b60b910c104b054305c81d167c1711c27c6 /llvm/lib/CodeGen/MachineFunction.cpp
parenteb755df5c27f5687a4f43a62e7eb0713c3f8f030 (diff)
downloadllvm-59029b9eef23c72d904f9a6b182c5cd4402a69c5.zip
llvm-59029b9eef23c72d904f9a6b182c5cd4402a69c5.tar.gz
llvm-59029b9eef23c72d904f9a6b182c5cd4402a69c5.tar.bz2
[RS4GC] Handle uses of extractelement for conversion from vector to scalar base
As mentioned in the comments, extractelement is special since we actually want a scalar base for that element we extracted from the vector (i.e. not a vector base). This same logic should apply to uses of the extractelement such as phis and selects which have the same BDV as the extractelement. Howeber, for these uses we conservatively mark the BDV state as conflict, since setting the EE's new base BDV does not always dominate these uses. Added testcase showcases the problem where the BDV identification chokes on the incorrect cast from vector to scalar for the phi use of extractelement. Tests-Run: make check, internal fuzzer testing Reviewers: reames, skatkov, dantrushin Reviewed-By: dantrushin Differential Revision: https://reviews.llvm.org/D75704
Diffstat (limited to 'llvm/lib/CodeGen/MachineFunction.cpp')
0 files changed, 0 insertions, 0 deletions