[llvm-dev] libLTO C API stability policy
Dave Bozier via llvm-dev
llvm-dev at lists.llvm.org
Tue Oct 4 03:45:11 PDT 2016
Hi Mehdi,
We use the libLTO C API for our linker and binutils here at Sony.
Cheers,
Dave
On Mon, Oct 3, 2016 at 6:59 PM, Mehdi Amini via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi Kevin,
>
> > On Oct 3, 2016, at 10:49 AM, Kevin Enderby <enderby at apple.com> wrote:
> >
> > Hello Mehdi,
> >
> > Sorry for the delayed reply I was out on vacation for that last few days.
> >
> > As Pete Cooper already commented, the Apple cctools project (aka the
> “binutils” stuff), make use of the libLTO C API.
> >
> > At this time do you want to know an exact list of each API in use? It
> is not clear from your email below exactly what you are after at this point
> in time other than to identify who are the stakeholders. On that I do care
> about the libLTO C API so we don’t break the uses in the Apple cctools
> project.
>
> I’d like to establish a windows of deprecation of APIs.
> I assume that Apple’s binutils and ld64 have the same constraint/use-cases
> (but maybe I’m missing something).
>
> Right now I’m more interested to collect the non-Apple (non-DT) users and
> their constraints ;-)
>
> Thanks,
>
> —
> Mehdi
>
>
>
> >
> >> 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
> >
>
> _______________________________________________
> 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/20161004/0304deb5/attachment.html>
More information about the llvm-dev
mailing list