<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/56716>56716</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            Move COFF options parser from JITLink into libObject
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          lhames
      </td>
    </tr>
</table>

<pre>
    https://reviews.llvm.org/D130276 introduces a COFF options parser into JITLink to enable it to handle `export`, `alternatename` and other options. The parser should probably be moved to libObject long term, since it's important for interpreting the full meaning of a COFF relocatable object file.

We should also check whether the options parser could be brought up to parity with LLD's option parser, in which case that project might be able to share the (future) libObject options parser too.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxtU01vnDAQ_TXmMipizfJ14JBmtVKrVLlE6tmGYe3G2Mg22ebfd-xs0iqqhGDGzLz3ZnhIN7-OKsYtsPqO8TNdHl80XkNpzMtaOn-ho9OhrnjXgrbRu3mfMICA-8fzGdwWtbMBNuED-lTg4Pu3pwdtn4FCtEIaBB1TooSdKWFthb835yMFjN-nXJiI3opI5StSDlQJLipCvBGU8KTwnSUot5sZNu8kwb-CRFjdC86JxGj5KH_hFME4ewHCXRNJ0HZKOhjvAug10QsbYXFZM_rNY9SpnliW3RhYUdh04Jb3UT0aN4mYB3JvFIs2WLLqxKq7t_tPfBcnTHAwKZye4aowj5KwP-1ryrWkX3q3X1SEfUtD0FsdX-Gqo4KHh1MW_dZ5a0wjaUvIelIwiYAELmLaSNa16oRFsFksAQYlPGYBjPfLHnePjA__LOuTruhcWeB4aJu-G3jXD8U81vNQD6KIOhocf9C-_-uAxbv1wwHZDh8kxe7NJ69daMJdlpOjj3ROhrs9vtwmoVSHsGOgoGm7Q1uoUc591zVLjfzYH5e5GXhf97zhbdXIqj8cCiMkmjCy5ivj3OIVMgTFrDkVeuQV51VHDfWx5UM5yPbIOR9QLJWYGsmOFa5Cmw__F37MkuR-CfTS6BD__hyFCEFfLGKmI3yxR-WoQ5GTQ5GZx6z8D2JwJ3M">