<div dir="ltr">'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.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 21, 2014 at 2:12 PM, Eric Christopher <span dir="ltr"><<a href="mailto:echristo@gmail.com" target="_blank">echristo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote"><span class="">On Sun Dec 21 2014 at 10:13:07 AM Philip Reames <<a href="mailto:listmail@philipreames.com" target="_blank">listmail@philipreames.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
<div>On 12/18/2014 06:58 PM, Kevin
Modzelewski wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'd be interested in that, though would it be an
issue if it doesn't have an in-tree user?</div>
</blockquote></div><div bgcolor="#FFFFFF" text="#000000">
Quite possibly. It would bit rot if nothing else. <br>
<br>
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.<br>
<br></div></blockquote><div><br></div></span><div>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. </div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-eric</div></font></span><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
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. <br></div><div bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Dec 15, 2014 at 11:09 PM,
Sanjoy Das <span dir="ltr"><<a href="mailto:sanjoy@playingwithpointers.com" target="_blank">sanjoy@playingwithpointers.com</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Our use case for LLVM requires us to parse the .eh_frame
sections<br>
emitted by MCJIT (for callee-saved-register spill slots,
amongst other<br>
things). Does it make sense to have an in-tree parser for
.eh_frame,<br>
given that it will make such tasks a lot easier?<br>
<br>
-- Sanjoy<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a>
<a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
LLVM Developers mailing list
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a>
</pre>
</blockquote>
<br>
</div>
______________________________<u></u>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/llvmdev</a><br>
</blockquote></span></div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div>