[llvm-dev] [cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community

Jake Ehrlich via llvm-dev llvm-dev at lists.llvm.org
Mon Apr 9 13:51:08 PDT 2018


I'm also going to chime in here pretty late. I've been thinking about
proposing a tool (which I've been calling llvm-abitool) to do many of these
same things. I would be willing to contribute the ELF part of this tool and
get that up and running.

On Sat, Apr 7, 2018 at 9:12 PM John Ericson via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> To belatedly second Juergen, yes I think the concept of TBD files is
> great, and not just useful to the specific XCode situation of
> proprietary libraries. For example the mapfiles[1] of Illumos are
> exactly analogous and used not because the libc of Illumos is closed
> source (it isn't) but rather to ensure comparability across Illumos
> versions. The libc (shared library) ABI of Illumos is the stable
> interface rather than the syscall ABI like Linux, so ensuring linkers
> see *only* see the export list at build time prevents the abstraction
> from leaking and unintended incompatibilities being utilized.
>
> Beyond my general esteem for using export lists for hermetic builds, I'm
> working on automated native and cross builds for Darwin, and it would be
> a lot more convenient if this was part of LLVM.
>
> So what happened to this? I searched TAPI on differential and didn't see
> anything.  Given the general need for something like a standardized
> export list to feed a linker instead of the shared library itself, and
> the utility of this specific format given its use by a major platform, I
> think it definitely should be upstreamed.
>
> John
>
> [1]
>
> https://github.com/joyent/illumos-joyent/blob/master/usr/src/lib/README.mapfiles
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180409/21ffce44/attachment.html>


More information about the llvm-dev mailing list