<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 20, 2020, at 1:47 PM, James Y Knight via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">But the most recent NaCL toolchain release is based on LLVM 3.7 from 2015.<div class=""><br class=""></div><div class="">Unless you're planning to upgrade the NaCL toolchain to use a new release based on LLVM devhead (which would seem a rather expensive thing to attempt now, given the plan to desupport it in a year), I don't think keeping the code in LLVM is actually useful for anyone at this point.</div></div></div></blockquote><div><br class=""></div><div>Right, I think this is the key issue. If the community cannot use the code that is in tree, there isn’t a strong reason for the community to maintain it.</div><div><br class=""></div><div>-Chris</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 20, 2020 at 4:22 PM Derek Schuff via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">Hi Fangrui,<div class="">As you noted we are working on helping our NaCl users transition to WebAssembly and new web APIs that cover the functionality offered by NaCl. In terms of actually turning down the platform features, we recently announced a timeline at <a href="https://blog.chromium.org/2020/01/moving-forward-from-chrome-apps.html" target="_blank" class="">https://blog.chromium.org/2020/01/moving-forward-from-chrome-apps.html</a>. </div><div class=""><br class=""></div><div class="">In terms of LLM, I would prefer to keep the support we have in the tree until we complete the turndown as long as the support isn't unusually onerous. Not all of our NaCl toolchain code is upstream, but we are actually about to redo part of our current downstream code soon to improve Chromium's C++ support until we complete the platform turndown. And of course we continue to be available to support it upstream as needed, especially if there is some particular problem you're looking to solve by removing this code. </div><div class="">Feel free to contact me directly as well (aside from the usual channels like this list of course) if you want more on NaCl or PNaCl.</div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 18, 2020 at 10:25 PM Petr Hosek via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><div dir="ltr" class="">On Sat, Apr 18, 2020 at 7:43 PM Fangrui Song via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a>> wrote:<br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br class="">
<br class="">
LLVM/Clang supports an OS called 'NaCl' (llvm/include/llvm/ADT/Triple.h).<br class="">
It apparently hasn't had any development since 2015.<br class="">
<br class="">
This page <a href="https://developer.chrome.com/native-client/migration" rel="noreferrer" target="_blank" class="">https://developer.chrome.com/native-client/migration</a><br class="">
mentions that NaCl is deprecated.<br class="">
<br class="">
Is it still used? If not, I would propose that we remove it.<br class="">
I created a patch <a href="https://reviews.llvm.org/D78441" rel="noreferrer" target="_blank" class="">https://reviews.llvm.org/D78441</a> which I think can<br class="">
delete 90% of the related code.<br class="">
<br class="">
There are still a few references left (noticeably aligned bundling in<br class="">
MC) <a href="https://sites.google.com/a/chromium.org/dev/nativeclient/pnacl/aligned-bundling-support-in-llvm" rel="noreferrer" target="_blank" class="">https://sites.google.com/a/chromium.org/dev/nativeclient/pnacl/aligned-bundling-support-in-llvm</a><br class="">
I will delete that as a follow-up.<br class=""></blockquote><div class=""><br class=""></div><div class="">AFAIK aligned bundling has other users (e.g. the author of <a href="https://reviews.llvm.org/D19924" target="_blank" class="">https://reviews.llvm.org/D19924</a> mentioned interested in using bundle locked groups for Hexagon) so its removal should be probably treated as a separate proposal.</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
_______________________________________________<br class="">
cfe-dev mailing list<br class="">
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a><br class="">
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class="">
</blockquote></div></div>
_______________________________________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
</blockquote></div>
_______________________________________________<br class="">
LLVM Developers mailing list<br class="">
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" class="">llvm-dev@lists.llvm.org</a><br class="">
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">
</blockquote></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></body></html>