Definitely interested, you can probably throw it into the stuff in lib/DebugInfo if that makes sense.<br><br><div>-eric</div><br><div class="gmail_quote">On Thu Dec 18 2014 at 3:37:55 PM Sanjoy Das <<a href="mailto:sanjoy@playingwithpointers.com">sanjoy@playingwithpointers.com</a>> wrote:<br><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>
______________________________<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></div>