[PATCH] D60974: Clang IFSO driver action.

[Puyan Lotfi via Phabricator via cfe-commits]

plotfi added a comment.

In D60974#1485417 <https://reviews.llvm.org/D60974#1485417>, @jakehehrlich wrote:

> Background:
>  There are two parts to this. TextAPI is a public interface of textual representations for these sorts of files that already exists in llvm. There exist ELF and MachO textual representations currently. llvm-elfabi is a tool for 1) Creating Stubs 2) Creating .tbe (the TextAPI fully linked ELF format) files 3) Converting between them and 4) Analyzing the details of the formats.
>
> You asked about the format I proposed here, not the already accepted .tbe format. The format proposed here could be added to TextAPI where it could subsequently be used in both Clang and a tool that would use the llvm-elfabi code to create stubs. I imagine the flags needed for this new tool would be very differnet from what llvm-elfabi uses or would use in the future so we'd probably want a second symlink the behaved very differently.
>
> It can currently read ELF and .tbe files and can currently write .tbe files. I'll have the basics of ELF writing up for review by the end of the day and that will, for the next month or two be my primary work which should likely see it close to stabilized. I'd expect landing the basics of ELF writing to take another week or two since its somewhat involved and I'll likely need to split the patches up from what I have. Given that no such writer currently exists this should put a version of your tool well ahead of schedule. Such are the wonderful benefits of open source.


Good, thanks for confirming this. For the format you proposed here, do you think that should be consumed by llvm-elfabi or by a secondary tool that generates a final merged tbe to be consumed by llvm-elfabi?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D60974/new/

https://reviews.llvm.org/D60974