<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Niklas,</div><div><br></div>The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to detect the cpu. My guess is the proper fix is on the RoboVM side to handle the change.<div><br></div><div>Jim, can you confirm?<br><div><br></div><div>Evan</div><div><br><div><div>On Jun 1, 2014, at 1:45 PM, Niklas Therning <<a href="mailto:niklas@therning.org">niklas@therning.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which can be applied to the current release_34 branch (tested against the release_34 branch in llvm-mirror). With this patch the attached reg-alloc-test.ll file doesn't fail with the "<span style="font-family:arial,sans-serif;font-size:13px">LLVM ERROR: ran out of registers during register allocation</span>" error any longer. I haven't run any llvm tests to make sure this patch doesn't break anything else but as far as I can see it doesn't at least break anything when used in RoboVM.<div>
<br></div><div>Is it too late to get this into 3.4.2? Is there anything else I can do to make it easier for you to include this patch in 3.4.2 or the next possible point release?</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, May 14, 2014 at 3:25 PM, Renato Golin <span dir="ltr"><<a href="mailto:renato.golin@linaro.org" target="_blank">renato.golin@linaro.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 14 May 2014 14:15, Niklas Therning <<a href="mailto:niklas@therning.org">niklas@therning.org</a>> wrote:<br>
> I can confirm that this regression has been fixed in trunk. Should I report<br>
> this as a bug in 3.4?<br>
<br>
</div>The 3.4.2 release is coming, you might want to consider finding the<br>
patches responsible for the fix and proposing it for back-porting.<br>
<br>
Please email Tom (cc'd) if you end up with a proposal.<br>
<br>
cheers,<br>
--renato<br>
</blockquote></div><br></div>
<span><reg-alloc-regression.patch></span><span><reg-alloc-test.ll></span>_______________________________________________<br>LLVM Developers mailing list<br><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></blockquote></div><br></div></div></body></html>