hvdijk wrote: The `version_check` failure is because the repo was expected to be updated after the last release, but it has not yet been. Based on https://discourse.llvm.org/t/potential-abi-break-in-19-1-3/82865 I assume this is because it is not yet decided what the next version number is supposed to be? Either way, I think we can ignore that error.
But based on that discussion: this PR is also technically an ABI break. It breaks symbols that are public for technical reasons, but are meant to only be used by LLVM internally. What is the policy on that? Is that something that can go into `19.1.y`, or does that have to wait until `19.2.y`? (No preference either way from me.) https://github.com/llvm/llvm-project/pull/114786 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
