https://llvm.org/docs/DeveloperPolicy.html#c-api-changes doesn't say we
guarantee strict backward compatibility, in fact it implies the opposite,
that's it's "best effort" but can be broken when necessary
(except within a
release branch).
On Tue, Mar 23, 2021 at 12:26 PM via llvm-dev <llvm-dev at lists.llvm.org>
wrote:
> > For https://reviews.llvm.org/D99173 I need to introduce an extra
> > 'LLVMModuleRef' argument to
'LLVMIntrinsicCopyOverloadedName',
> > so that we correctly handle intrinsics with arguments based on
> > unnamed types.
> >
> > Can this be done ? Or is it recommended to add a
> > 'LLVMIntrinsicCopeOverloadedName2' with the extra argument ?
> > And keep the original one for backwards compatibility ?
>
> The C API has a strict backward compatibility rule; you will need
> to add a new function that has the additional parameter.
>
> --paulr
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://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/20210323/29507215/attachment.html>