summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorJuneyoung Lee <aqjune@gmail.com>2020-01-15 01:11:20 +0900
committerJuneyoung Lee <aqjune@gmail.com>2020-01-15 03:20:53 +0900
commit3e32b7e12701de772b1cdf855b42253650a1e997 (patch)
treecfaa7f905c9dcbf2145a9e646ff929892f6ab608 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parent40c5bd4212a51216a489fdaaf59060921d677009 (diff)
downloadbcm5719-llvm-3e32b7e12701de772b1cdf855b42253650a1e997.tar.gz
bcm5719-llvm-3e32b7e12701de772b1cdf855b42253650a1e997.zip
[InstCombine] Let combineLoadToNewType preserve ABI alignment of the load (PR44543)
Summary: If aligment on `LoadInst` isn't specified, load is assumed to be ABI-aligned. And said aligment may be different for different types. So if we change load type, but don't pay extra attention to the aligment (i.e. keep it unspecified), we may either overpromise (if the default aligment of the new type is higher), or underpromise (if the default aligment of the new type is smaller). Thus, if no alignment is specified, we need to manually preserve the implied ABI alignment. This addresses https://bugs.llvm.org/show_bug.cgi?id=44543 by making combineLoadToNewType preserve ABI alignment of the load. Reviewers: spatel, lebedev.ri Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D72710
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud