Skip to content
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

release/19.x: [libclang] Fix symbol version of getBinaryOpcode functions (#101820) #101824

Merged
merged 1 commit into from
Aug 4, 2024

Conversation

llvmbot
Copy link
Collaborator

@llvmbot llvmbot commented Aug 3, 2024

Backport 2bae7ae

Requested by: @Endilll

@llvmbot llvmbot added this to the LLVM 19.X Release milestone Aug 3, 2024
@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 3, 2024

@Endilll What do you think about merging this PR to the release branch?

@llvmbot llvmbot requested a review from Endilll August 3, 2024 14:02
@llvmbot llvmbot added the clang Clang issues not falling into any other category label Aug 3, 2024
@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 3, 2024

@llvm/pr-subscribers-clang

Author: None (llvmbot)

Changes

Backport 2bae7ae

Requested by: @Endilll


Full diff: https://github.com/llvm/llvm-project/pull/101824.diff

1 Files Affected:

  • (modified) clang/tools/libclang/libclang.map (+6-2)
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 {

Copy link

github-actions bot commented Aug 3, 2024

⚠️ We detected that you are using a GitHub private e-mail address to contribute to the repo.
Please turn off Keep my email addresses private setting in your account.
See LLVM Discourse for more information.

Copy link
Contributor

@Endilll Endilll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't consider this critical, but I can see this becoming a source of confusion for a long time.

…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)
@tru tru merged commit 4a211ac into llvm:release/19.x Aug 4, 2024
9 of 12 checks passed
Copy link

github-actions bot commented Aug 4, 2024

@Endilll (or anyone else). If you would like to add a note about this fix in the release notes (completely optional). Please reply to this comment with a one or two sentence description of the fix. When you are done, please add the release:note label to this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang Clang issues not falling into any other category
Projects
Development

Successfully merging this pull request may close these issues.

4 participants