[llvm-dev] libLTO C API stability policy
Tobias Edler von Koch via llvm-dev
llvm-dev at lists.llvm.org
Tue Jan 31 14:10:38 PST 2017
Just saw the recent replies to this old thread, so just as an FYI... We
(QuIC Hexagon and ARM) are moving away from libLTO and are anticipating
to complete the move to the C++ API imminently, so I don't have any
particular concerns about backward compatibility of the C API on our side.
On 09/30/2016 03:18 PM, Mehdi Amini via llvm-dev 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!
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
More information about the llvm-dev