I'll work on another round with the feedback so far. On SundayFeb 24, at Feb 24, Sunday11:24 PM, Evan Cheng wrote:> 1. __LTO__ -> LLVM_C_LTOThis 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. -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080225/7bd5b3c5/attachment.html>
On Feb 25, 2008, at 11:02 AM, Nick Kledzik wrote:> I'll work on another round with the feedback so far. > > > On SundayFeb 24, at Feb 24, Sunday11:24 PM, Evan Cheng wrote: >> 1. __LTO__ -> LLVM_C_LTO > > 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.Ok, that makes sense. Ignore my comments about naming convention, etc. then. However, does this mean the interface should not be part of llvm if it's truly compiler neutral? Evan> > -Nick > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On Mon, 25 Feb 2008, Evan Cheng wrote:>> lto_ interface and it would just work with the linker. Therefore, >> although this implementation is llvm specific, the interface is not. > > Ok, that makes sense. Ignore my comments about naming convention, etc. > then. However, does this mean the interface should not be part of llvm > if it's truly compiler neutral?The goal is for it to be compiler neutral, but since LLVM is the only compiler that supports it, it is mostly a theoretical exercise. When the second compiler comes along that wants to support LTO, we can figure out where it should live. Until then, living in the LLVM repo makes sense to me, -Chris -- http://nondot.org/sabre/ http://llvm.org/