[llvm-bugs] [Bug 45116] New: [DAGCombine] Replace some uses of getABITypeAlignment with allowsMemoryAccess

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=45116

            Bug ID: 45116
           Summary: [DAGCombine] Replace some uses of getABITypeAlignment
                    with allowsMemoryAccess
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Common Code Generator Code
          Assignee: unassignedbugs at nondot.org
          Reporter: llvm-dev at redking.me.uk
                CC: craig.topper at gmail.com, efriedma at quicinc.com,
                    lebedev.ri at gmail.com, llvm-bugs at lists.llvm.org,
                    nikita.ppv at gmail.com, spatel+llvm at rotateright.com

We are often using getABITypeAlignment to determine whether a merged load/store
is safe, which seems to be overkill as in most cases we aren't dealing with ABI
call requirements, we should be able to use allowsMemoryAccess (and maybe a
fast load check) instead.

DAGCombiner::CombineConsecutiveLoads
DAGCombiner::ReduceLoadOpStoreWidth
DAGCombiner::scalarizeExtractedVectorLoad
DAGCombiner::TransformFPLoadStorePair
LoadedSlice::canMergeExpensiveCrossRegisterBankCopy


This should be useful for platforms like x86 where unaligned scalar loads are
the norm.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200305/96bdc82e/attachment.html>