<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:renato.golin@linaro.org" title="Renato Golin <renato.golin@linaro.org>"> <span class="fn">Renato Golin</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - inline asm global registers compatibility to gcc+icc"
href="https://llvm.org/bugs/show_bug.cgi?id=31005">bug 31005</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;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - inline asm global registers compatibility to gcc+icc"
href="https://llvm.org/bugs/show_bug.cgi?id=31005#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - inline asm global registers compatibility to gcc+icc"
href="https://llvm.org/bugs/show_bug.cgi?id=31005">bug 31005</a>
from <span class="vcard"><a class="email" href="mailto:renato.golin@linaro.org" title="Renato Golin <renato.golin@linaro.org>"> <span class="fn">Renato Golin</span></a>
</span></b>
<pre>Closing this as wontfix because that's our community's current position.
If anyone wants to change this position they'll have to:
1. Create a downstream prototype where registers can be allocated and
deallocated by the user on a function and module scope without destroying the
register allocators (plural) job.
2. Send an RFC to the list, with the design decisions taken to make that work,
and work with the community to adapt your downstream implementation to work
that way.
3. After addressing all the community's feedback, send a list of small and
incremental patches, implementing the functionality with enough tests to cover
each step, and making sure none of them break the build on their own, ie.
isolated and working changes.
4. Work with the community to push the patches upstream, address reviews, etc.
As it stands, the community doesn't need, nor want, arbitrary global named
registers, so don't expect people to implement that for you. We have
successfully convinced users to change their code, and most of the time to
better code, proving that this feature is not needed at all.
If it is needed for you, and you can show that to the community, you'll have to
go through the proper upstreaming process described above.</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>