[LLVMdev] interest in an .eh_frame parser in llvm?

Reid Kleckner rnk at google.com
Mon Dec 22 11:02:37 PST 2014


'llvm-readobj -u' supports dumping ARM EHABI unwind info and the Windows
UNWIND_INFO codes from .xdata, so this seems like a natural thing to hook
up there as well.

On Sun, Dec 21, 2014 at 2:12 PM, Eric Christopher <echristo at gmail.com>
wrote:

>
>
> On Sun Dec 21 2014 at 10:13:07 AM Philip Reames <listmail at philipreames.com>
> wrote:
>
>>
>> On 12/18/2014 06:58 PM, Kevin Modzelewski wrote:
>>
>> I'd be interested in that, though would it be an issue if it doesn't have
>> an in-tree user?
>>
>> Quite possibly.  It would bit rot if nothing else.
>>
>> At minimum, we need a dumper tool - possibly an option to an existing one
>> - which produces human readable output and a bunch of lit tests to ensure
>> it's not broken by other changes.  In particular, we need to make sure that
>> the in tree parser can parse the sections llvm itself is producing.
>>
>>
> Yeah, that's why I was mentioning throwing it into lib/DebugInfo. That way
> llvm-dwarfdump or llvm-objdump could dump the sections that we produce.
>
> -eric
>
>
>> p.s. One thing I think we need to be very careful to document is that
>> this .eh_frame parser is version locked to the same version of llvm and is
>> only guaranteed to parse output from that version of llvm.  I'm not opposed
>> to trying to be more generic, but I suspect that would involve a lot more
>> work.
>>
>>
>> On Mon, Dec 15, 2014 at 11:09 PM, Sanjoy Das <
>> sanjoy at playingwithpointers.com> wrote:
>>>
>>> Hi all,
>>>
>>> Our use case for LLVM requires us to parse the .eh_frame sections
>>> emitted by MCJIT (for callee-saved-register spill slots, amongst other
>>> things).  Does it make sense to have an in-tree parser for .eh_frame,
>>> given that it will make such tasks a lot easier?
>>>
>>> -- Sanjoy
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>>
>>
>>
>> _______________________________________________
>> LLVM Developers mailing listLLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.eduhttp://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>>
>>  _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141222/4f4e2770/attachment.html>


More information about the llvm-dev mailing list