Alexander Yermolovich via llvm-dev
2021-Jul-23 01:10 UTC
[llvm-dev] [RFC][Dwarf Library] Relocations for DWO sections
Hello I observed when DWARF Context is created for DWO object (split dwarf single mode), that relocations for .debug_info are processed and are stored in a map. This adds quite a bit of memory overhead. This doesn't seem like it is needed for DWO Context. Context created through API DWARFContext::getDWOContext. Am I missing something? Illustrative patch to fix this: https://reviews.llvm.org/D106624 Thank you, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210723/13ebb300/attachment.html>
David Blaikie via llvm-dev
2021-Jul-23 14:41 UTC
[llvm-dev] [RFC][Dwarf Library] Relocations for DWO sections
General premise sounds correct to me (that we shouldn't be processing those sections, etc). I've replied to the patch - thanks for taking a look at this! (out of curiosity: What are you using Split DWARF single mode for (if you can speak to the application)?) On Thu, Jul 22, 2021 at 9:10 PM Alexander Yermolovich via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Hello > > I observed when DWARF Context is created for DWO object (split dwarf > single mode), that relocations for .debug_info are processed and are stored > in a map. This adds quite a bit of memory overhead. This doesn't seem like > it is needed for DWO Context. Context created through > API DWARFContext::getDWOContext. Am I missing something? > > Illustrative patch to fix this: > https://reviews.llvm.org/D106624 > > Thank you, > Alex > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210723/dc8588f5/attachment.html>