[PATCH] D19236: Add DITypeIndex for CodeView and emit it for locals
Reid Kleckner via llvm-commits
llvm-commits at lists.llvm.org
Wed Apr 20 10:43:59 PDT 2016
On Tue, Apr 19, 2016 at 6:30 PM, David Blaikie <dblaikie at gmail.com> wrote:
> What's the goal/advantage of having CUs not directly reference type
> streams?
>
It seemed nice to keep it decoupled. I also figured this would help us be
lazier about deserializing the type stream like it did for DISubprograms,
but maybe that is misguided and premature.
> Practically speaking, LTO will likely need to be format-aware for
> practical/realistic performance reasons (the same reason all the work has
> gone into deduplicating types in the current metadata scheme - without it,
> LTO is impractical).
>
Ultimately, yes, I think we will want to make LTO do format aware type
stream merging. However, a normal 64-bit linker generally has enough memory
and address space to map all of its inputs, and it doesn't need to perform
type merging. Obviously, LTO uses more memory than linking, but I think
we'll be able to do a fair amount of useful LTO before we have to cross the
type stream merging bridge.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160420/72b66a90/attachment.html>
More information about the llvm-commits
mailing list