[LLVMdev] DebugInfo library and relocations in the .debug_line section
Eric Christopher
echristo at gmail.com
Thu Jan 10 14:43:17 PST 2013
That relocation handling is only done for the llvm-dwarfdump binary. MCJIT
handles relocations a bit different. I think you just need to go ahead and
allow the MCJIT relocation handling machinery to work on non-alloc sections
and it should go ahead and handle these just fine, unless you're using the
existing stuff in lib/DebugInfo to print out information or something?
If this isn't what you're doing can you give me a bit more information on
your current code?
-eric
On Wed, Jan 9, 2013 at 4:53 PM, Kaylor, Andrew <andrew.kaylor at intel.com>wrote:
> I’m working on adding source-based profiling support for MCJIT and in
> the process of implementing this, I came across a test case where an object
> is being generated that wants to have relocations applied to the
> .debug_line section. I see in the DebugInfo code that it currently only
> supports relocations applied to either the .debug_info or the
> .debug_info.dwo section.****
>
> ** **
>
> Can anyone give me an overview of what I would need to do to extend this
> to handle the .debug_line section also?****
>
> ** **
>
> Thanks,****
>
> Andy****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130110/9484ae12/attachment.html>
More information about the llvm-dev
mailing list