-
Notifications
You must be signed in to change notification settings - Fork 11.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[libclang] Fix symbol version of getBinaryOpcode
functions
#101820
Conversation
@llvm/pr-subscribers-clang Author: Jannick Kremer (DeinAlptraum) ChangesFull diff: https://github.com/llvm/llvm-project/pull/101820.diff 1 Files Affected:
diff --git a/clang/tools/libclang/libclang.map b/clang/tools/libclang/libclang.map
index 91c329b5765d4..371fe512ce71c 100644
--- a/clang/tools/libclang/libclang.map
+++ b/clang/tools/libclang/libclang.map
@@ -54,8 +54,6 @@ LLVM_13 {
clang_Cursor_Evaluate;
clang_Cursor_getArgument;
clang_Cursor_getBriefCommentText;
- clang_Cursor_getBinaryOpcode;
- clang_Cursor_getBinaryOpcodeStr;
clang_Cursor_getCXXManglings;
clang_Cursor_getCommentRange;
clang_Cursor_getMangling;
@@ -430,6 +428,12 @@ LLVM_17 {
clang_getCursorUnaryOperatorKind;
};
+LLVM_19 {
+ global:
+ clang_Cursor_getBinaryOpcode;
+ clang_Cursor_getBinaryOpcodeStr;
+};
+
# Example of how to add a new symbol version entry. If you do add a new symbol
# version, please update the example to depend on the version you added.
# LLVM_X {
|
getBinaryOpcode
functions
I wrote a description to provide readers some context. In general PRs without descriptions are discouraged. |
/cherry-pick 2bae7ae |
…1820) llvm#98489 resurrected an [old patch](https://reviews.llvm.org/D10833) that was adding new libclang functions. That PR got merged with old `LLVM_13` symbol versions for new functions. This patch fixes this oversight. (cherry picked from commit 2bae7ae)
/pull-request #101824 |
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/41/builds/1076 Here is the relevant piece of the build log for the reference:
|
The failure is not related to this PR
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/4/builds/1144 Here is the relevant piece of the build log for the reference:
|
This one is the same, consequently not related:
|
…1820) llvm#98489 resurrected an [old patch](https://reviews.llvm.org/D10833) that was adding new libclang functions. That PR got merged with old `LLVM_13` symbol versions for new functions. This patch fixes this oversight. (cherry picked from commit 2bae7ae)
…1820) llvm#98489 resurrected an [old patch](https://reviews.llvm.org/D10833) that was adding new libclang functions. That PR got merged with old `LLVM_13` symbol versions for new functions. This patch fixes this oversight.
…1820) llvm#98489 resurrected an [old patch](https://reviews.llvm.org/D10833) that was adding new libclang functions. That PR got merged with old `LLVM_13` symbol versions for new functions. This patch fixes this oversight.
#98489 resurrected an old patch that was adding new libclang functions. That PR got merged with old
LLVM_13
symbol versions for new functions. This patch fixes this oversight.