<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 12/18/2014 06:58 PM, Kevin
      Modzelewski wrote:<br>
    </div>
    <blockquote
cite="mid:CAO=oM6u=y98KsLWUkCYsngSmHsEN2RrGwX9GMETMkXLsJ4UMRg@mail.gmail.com"
      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>
    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>
    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>
    <blockquote
cite="mid:CAO=oM6u=y98KsLWUkCYsngSmHsEN2RrGwX9GMETMkXLsJ4UMRg@mail.gmail.com"
      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 moz-do-not-send="true"
                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 moz-do-not-send="true"
                href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> 
                     <a moz-do-not-send="true"
                href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
              <a moz-do-not-send="true"
                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 class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a>         <a class="moz-txt-link-freetext" href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>