Note that this change (and related changes) is nuking a huge amount of non-deprecated C API functions. It suggests using the LLVMBuild* versions, but those do not work without instantiating a builder, which typically does not exist on the global level. Allowing the user of the API to pass in a NULL builder would have made it more palatable, but as is the option is either to create a dummy builder for the global level (which isn't actually used! It's just to satisfy the contract of the LLVMBuild* functions) or try to do constant folding in the frontend. In addition the removal it also breaks all LLVM-C based bridges in other languages.

Note that I'm not really having a good environment to work on LLVM. I can submit changes I've tested to work with my frontend, but I don't know much about the unit tests in LLVM. If you don't want to accept this change because of the missing the tests, then perhaps we could have someone look at adding the tests?

Removed the default context method.

Just so I understand @arsenm: are API unit tests needed to approve this pull request? If so, who is planning on adding them? I mean the C API as it currently works cannot even correctly provide byval and sret according to spec.

In D97763#2597047, @arsenm wrote:

As far as I know we don't have any C API unit tests, but sorely need them if you want to try adding the first