<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:qcolombet@apple.com" title="Quentin Colombet <qcolombet@apple.com>"> <span class="fn">Quentin Colombet</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - i386: error: ran out of registers during register allocation"
href="https://llvm.org/bugs/show_bug.cgi?id=27809">bug 27809</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>qcolombet@apple.com
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>INVALID
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - i386: error: ran out of registers during register allocation"
href="https://llvm.org/bugs/show_bug.cgi?id=27809#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED INVALID - i386: error: ran out of registers during register allocation"
href="https://llvm.org/bugs/show_bug.cgi?id=27809">bug 27809</a>
from <span class="vcard"><a class="email" href="mailto:qcolombet@apple.com" title="Quentin Colombet <qcolombet@apple.com>"> <span class="fn">Quentin Colombet</span></a>
</span></b>
<pre>This message usually means you have over constrained inline asm statement.
I believe the problem here is that we do not have enough register available in
the allocatable space to fill all the argument of the inline asm statement.
I.e., at first glance, I do not think we have a free register for the ebp
register. The fact that is works when you remove it from the reserved set of
register would support that hypothesis.
Therefore, I would resolve this as invalid; you’re asking for infeasible inline
asm.</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>