<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
I'll work on another round with the feedback so far. <div><br class="webkit-block-placeholder"></div><div><br><div><div>On SundayFeb 24, at Feb 24, Sunday11:24 PM, Evan Cheng wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div>1. __LTO__ -> LLVM_C_LTO</div></span></blockquote></div><br><div>This one is actually interesting. The names started out with llvm in them, but then we realized that this was a generic interface from the linker to some foreign object file format. So, some other compiler could create an LTO shared object that exports the same lto_ interface and it would just work with the linker. Therefore, although this implementation is llvm specific, the interface is not.</div><div><br class="webkit-block-placeholder"></div><div>-Nick</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><br></div></div></body></html>