<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 29, 2017, at 5:01 PM, Kevin Enderby <<a href="mailto:enderby@apple.com" class="">enderby@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 29, 2017, at 1:11 PM, Peter Collingbourne <<a href="mailto:peter@pcc.me.uk" class="">peter@pcc.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Jun 29, 2017 at 12:17 PM, Rafael Avila de Espindola <span dir="ltr" class=""><<a href="mailto:rafael.espindola@gmail.com" target="_blank" class="">rafael.espindola@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Peter Collingbourne <<a href="mailto:peter@pcc.me.uk" target="_blank" class="">peter@pcc.me.uk</a>> writes:<br class="">
<br class="">
> That would be nice, but it might not be possible until we can drop<br class="">
> backwards compatibility with bitcode files that might not have a symbol<br class="">
> table. This may not happen for a while if I understand Apple's constraints<br class="">
> on backwards compatibility correctly.<br class="">
<br class="">
</span>Do you know if those requirements include llvm-nm and llvm-ar?<br class=""></blockquote><div class=""><br class=""></div><div class="">I have no idea, but I'm copying Kevin and Nick, who might know.</div></div></div></div></div></blockquote><div class=""><br class=""></div>I don’t know the constraints on backwards compatibility when it comes to bitcode files, Nick might know. The guy I would ask here is Bob Wilson who will be back from vacation soon.</div></div></div></blockquote><br class=""></div><div>Am I right that you’re suggesting that llvm-ar and llvm-nm could support only newer bitcode files that have symbol tables, while other uses of old bitcode files (e.g., for LTO) would continue to work? I can’t think of anything offhand that would be broken by that.</div><div><br class=""></div><div>Fred and Steven, can you think of anything?</div></body></html>