<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 3, 2014, at 2:09 PM, Tim Northover <<a href="mailto:t.p.northover@gmail.com" class="">t.p.northover@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" class="">Please let me know your feedback and steps to get it merged.<br class=""></blockquote><br class="">Could I ask who's going to maintain this backend? Targets without an<br class="">active LLVM sub-community behind them tend to slowly bit-rot until<br class="">everyone else gets fed up enough with fixing it when they refactor<br class="">things; they then get removed.<br class=""></div></blockquote>Also (using AMDGPU and AArch64 as recent examples), we tend to add new backends as experimental then move them to ALL_TARGETS after some period of time.<div class=""><br class=""></div><div class="">See <a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120827/149491.html" class="">http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120827/149491.html</a> for example. I can’t find the original ‘experimental targets’ email for the concept itself unfortunately.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Pete</div><blockquote type="cite" class=""><div class=""><br class="">Cheers.<br class=""><br class="">Tim.<br class="">_______________________________________________<br class="">llvm-commits mailing list<br class=""><a href="mailto:llvm-commits@cs.uiuc.edu" class="">llvm-commits@cs.uiuc.edu</a><br class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits<br class=""></div></blockquote></div><br class=""></div></body></html>