<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [DAGCombine] Replace some uses of getABITypeAlignment with allowsMemoryAccess"
href="https://bugs.llvm.org/show_bug.cgi?id=45116">45116</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[DAGCombine] Replace some uses of getABITypeAlignment with allowsMemoryAccess
</td>
</tr>
<tr>
<th>Product</th>
<td>libraries
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Common Code Generator Code
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>llvm-dev@redking.me.uk
</td>
</tr>
<tr>
<th>CC</th>
<td>craig.topper@gmail.com, efriedma@quicinc.com, lebedev.ri@gmail.com, llvm-bugs@lists.llvm.org, nikita.ppv@gmail.com, spatel+llvm@rotateright.com
</td>
</tr></table>
<p>
<div>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>