<html>
<head>
<base href="http://llvm.org/bugs/" />
</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 --- - ARM EABI divmod for 64-bit types"
href="http://llvm.org/bugs/show_bug.cgi?id=17192">17192</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>ARM EABI divmod for 64-bit types
</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>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Backend: ARM
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>renato.golin@linaro.org
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - clang doesn't produce ARM EABI-compliant modulo runtime function (32-bit types)"
href="show_bug.cgi?id=16387">Bug #16387</a> dealt with 32-bit (legal) types for __aeabi_*divmod() calls, but
since 64-bit types are not legal in the ARM back-end, it's more complicated and
could take considerably longer.
Two ways were attempted, one local to the ARM back-end with many
type-legalization hacks (such as merge/split pairs, new REM64/DIV64/DIVREM64
ARM-specific node types, and another in the generic LegalizeDAG, but with some
intrusive changes to how library calls are dealt with.
This bug entails both the investigation on the best way to achieve this, as
well as the actual work/patch/merge.</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>