[llvm-branch-commits] [clang] release/19.x: [libclang] Fix symbol version of `getBinaryOpcode` functions (#101820) (PR #101824)

[via llvm-branch-commits]

llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-clang

Author: None (llvmbot)

<details>
<summary>Changes</summary>

Backport 2bae7aeab42062e61d6f9d6458660d4a5646f7af

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
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 {

``````````

</details>


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