search for: r171428

...es. If I let clang finish > things and create an executable, both dwarfdump and llvm-dwarfdump show > unique load-based addresses for everything.**** > > ** > Right. This is pretty easy, especially if you just look at my last patch that added a new reloc handler for .debug_info.dwo (r171428). I've been meaning to do this, but it hasn't bubbled up to the top of my queue yet. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130110/bfa4ec80/attachment.html>

Actually, MCJIT doesn't perform relocations on debug sections. I'm not sure that would matter anyway. The place where I'm handling the debug information is outside MCJIT and the MCJIT relocation code isn't really accessible at that point. Right now, when MCJIT emits an object image, it broadcasts an event to any registered listeners indicating that an object was emitted, passing

...ss zero just like llvm-dwarf does. If I let clang finish things and create an executable, both dwarfdump and llvm-dwarfdump show unique load-based addresses for everything. Right. This is pretty easy, especially if you just look at my last patch that added a new reloc handler for .debug_info.dwo (r171428). I've been meaning to do this, but it hasn't bubbled up to the top of my queue yet. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130111/4121ef11/attachment.html>