[cfe-dev] [PATCH] Wrap clang modules inside Mach-O/ELF/COFF containers

Argyrios Kyrtzidis kyrtzidis at apple.com
Fri Dec 12 14:36:56 PST 2014


> On Dec 12, 2014, at 2:26 PM, Argyrios Kyrtzidis <kyrtzidis at apple.com> wrote:
> 
>> 
>> I’m concerned about this because a release build than never enables debug info should not have debug info getting generated. In the past couple of years we have gradually regressed compile-time performance of clang and this is a fact; I believe one part is a consequence of not being prudent enough and sticking to “pay only what you use”.
>> 
>> I don't see module creation as an issue here and I think this is a red herring.
> 
> I don’t follow what you mean, generating debug info unconditionally, even when it was not requested, is work that was not occurring before and has no use. Is “red herring” meaning you think the additional work will be insignificant ? I’d like to see the data against Cocoa.
> 

Another related point. libclang will be one of the clang clients that will have no need or use for debug info in modules, what is the compelling reason to have libclang needing to link to codegen and pay the price for debug info generation ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20141212/f0a208b9/attachment.html>


More information about the cfe-dev mailing list