<div dir="ltr">Not that I know of... if they break we can just ignore them :)<div><br></div><div>-eric</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Aug 24, 2018 at 7:06 AM Kit Barton via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for the feedback everyone. <div><br><div>Does anyone know if there are any remaining darwin/ppc build bots? I looked but could not find any yesterday. I think that is the last thing to take care of before committing the patches. </div><div><br></div><div>Thanks,</div><div><br></div><div>Kit</div></div></div><div dir="ltr"><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Aug 23, 2018 at 12:28 AM Chris Lattner <<a href="mailto:clattner@nondot.org" target="_blank">clattner@nondot.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">😥 it was nice knowing you darwin/ppc, but it is now time to say goodbye. +1 from me.<br>
<br>
-Chris<br>
<br>
<br>
> On Aug 20, 2018, at 12:42 PM, Kit Barton via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
> <br>
> Hi all,<br>
> I just posted two patches on phabricator to remove Darwin support from the POWER backend. <br>
> <br>
> I thought I had posted this on the dev mailing list some time ago, but I cannot find a reference to it now. <br>
> <br>
> The intention here is to cleanup the POWER backend. Darwin has not been supported on POWER for quite some time now, and we'd like to use this as an opportunity to clean up several aspects of the backend code. If there is any concerns with this, please let me know.<br>
> <br>
> As for the approach, the patch that I posted will issue an error message from the backend if you attempt to use the Darwin ABI on PPC. The intention is that once this patch lands, all of the Darwin-specific code paths will essentially be dead-code, and we can remove them on demand as we're touching various pieces of code. This cleanup should be done in stand-alone patches, but can be done as NFC changes and thus reviewed post-commit, whenever possible. <br>
> <br>
> I've cleaned up all of the test cases effected by this, mostly by converting them to a different powerpc target so as to not lose test coverage. There were a few tests that were ppc-darwin specific, which were removed.<br>
> <br>
> There is a companion patch to clean up test cases in Clang as well. I think we can use a similar approach for cleaning up ppc-specific darwin code in Clang, although I don't have a good idea right now for how much cleanup that will be.<br>
> <br>
> Thanks.<br>
> <br>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
<br>
</blockquote></div></div></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>