[llvm-dev] libLTO C API stability policy

Pete Cooper via llvm-dev llvm-dev at lists.llvm.org
Fri Sep 30 14:18:31 PDT 2016

Some of the macOS tools like nm also use libLTO to symbolicate bitcode.

CCing Kevin who owns these and will know the API in use.

> On Sep 30, 2016, at 1:18 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> Hi all,
> libLTO is exposing a very “stable” (in the sense of immutable) C API to be used by linkers (and binutils tools) that manipulate bitcode (like when performing LTO).
> I’m looking into relaxing the stability concern and design a policy for this API that would allow to deprecate and remove some the APIs exposed here. The MacOS linker (ld64) is one the users of libLTO, but there are others (Sony? Qualcomm? Anyone else?) that I think are also targeting this API.
> I’d like to identify stakeholders so that we can establish a new policy that would accomodate everyone as much as possible. So if you care about the libLTO C API, please speak-up!
> Thanks,
>> Mehdi
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

More information about the llvm-dev mailing list