[PATCH] D12685: Document the stability policy for LLVM-C APIs.

[Amaury SECHET via llvm-commits]

deadalnix added a comment.

@echristo Yes and no. My understanding of the proposal is that method can be removed. Let's get practical here. There is a proposal to move toward pointer being untyped, and type being on the instruction manipulating the pointer (GEP, load, ...).

It will require the C API to be updated. The current function to build a load is as follow :

  LLVMValueRef LLVMBuildLoad(LLVMBuilderRef builder, LLVMValueRef ptr);

What the proposal forbid, is to change this as :

  LLVMValueRef LLVMBuildLoad(LLVMBuilderRef builder, LLVMTypeRef type, LLVMValueRef ptr);

But, it is possible to introduce another function and remove the current, existing one :

  LLVMValueRef LLVMBuildTypedLoad(LLVMBuilderRef builder, LLVMTypeRef type, LLVMValueRef ptr);

The proposal does not force us to keep the old method. Simply to introduce a method with a new name rather than modifying the signature of the existing method.


http://reviews.llvm.org/D12685