[LLVMdev] Bitcode parsing performance
joel.gouly at gmail.com
Fri Jan 10 17:55:36 PST 2014
Kevin, both those files give me a 500 error, are you sure they're public?
On 10 January 2014 22:23, Kevin Modzelewski <kmod at dropbox.com> wrote:
> Ok, I updated to trunk and reran (same results); here are the original and
> stripped bitcode files:
> On Fri, Jan 10, 2014 at 6:05 AM, Rafael Espíndola <
> rafael.espindola at gmail.com> wrote:
>> On 10 January 2014 03:09, Sean Silva <chisophugis at gmail.com> wrote:
>> > This Summer I was working on LTO and Rafael mentioned to me that debug
>> > is not lazy loaded, which was the cause for the insane resource usage I
>> > seeing when doing LTO with debug info. This is likely the reason that
>> > lazy loading was so ineffective for your debug build.
>> > Rafael, am I remembering this right/can you give more information? I
>> > that this will have to get fixed before pitching LLD as a turnkey LTO
>> > solution (not sure where in the priority list it is).
>> In the case of LTO, there were two main issues.
>> * Duplicate type debug information.
>> * All metadata (including debug info) is loaded eagerly.
>> As Eric mentioned, we can now merge type debug info from multiple
>> translation units, which results in a smaller total size. Kevin, what
>> llvm version are you using? Do you get a smaller combined bitcode with
>> The issue of loading all of the debug info ahead of time is still
>> there. We will need to fix that at some point or reduce its size
>> further so that the impact is small enough.
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev