These deprecated functions are incompatible with opaque pointers, and have replacements that accept an explicit type. Drop them now as a final warning to consumers of the C API to migrate their code (while LLVMGetElementType still exists as a temporary workaround).
Details
Details
- Reviewers
deadalnix aeubanks - Group Reviewers
Restricted Project - Commits
- rG279618241822: [llvm-c] Remove C API functions that are incompatible with opaque pointers
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
There are, but the tests have already been migrated to use opaque pointers.
As a side note, I've created https://discourse.llvm.org/t/rfc-remove-the-go-bindings/65725 to drop the Go bindings, which are clearly unmaintained (still no support for opaque pointers).
Comment Actions
apologies, but can we delay this? I've migrated Google internally to use opaque pointers with clang (after fixing various miscompiles), but we still have non-clang LLVM API users that are using these. I'm in the process of migrating them off legacy APIs (or dropping them altogether) but it'll take some time
Comment Actions
Rebase. This is now down to the C API removals only, and no longer requires changes to other bindings.