-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
GH-45132: [C++][Gandiva] Update LLVM to 18.1 #45114
base: main
Are you sure you want to change the base?
Conversation
|
|
Could you open a new issue for this? |
|
|
|
We have arrow/cpp/src/gandiva/engine.cc Lines 159 to 177 in f5c340b
Can we register |
Good idea, I'll try it. |
150d723
to
3bb3cc0
Compare
3bb3cc0
to
e77fae5
Compare
I didn't have any luck trying to register the symbols since this error was happening when creating the llvm object, before registration could be done. My latest change updates to llvm 18.1 which seems to fix the symbol issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow! LLVM 18.1 has a fix of this!?
BTW, can we update our default LLVM?
diff --git a/.env b/.env
index 0651d189c2..73644c0d1f 100644
--- a/.env
+++ b/.env
@@ -62,8 +62,7 @@ GCC=
HDFS=3.2.1
JDK=11
KARTOTHEK=latest
-# LLVM 12 and GCC 11 reports -Wmismatched-new-delete.
-LLVM=14
+LLVM=18
MAVEN=3.8.7
NODE=18
NUMBA=latest
ARG LLVM=18 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that we don't need this. (This isn't used.)
@@ -89,7 +89,7 @@ TZ=UTC | |||
# Used through docker-compose.yml and serves as the default version for the | |||
# ci/scripts/install_vcpkg.sh script. Prefer to use short SHAs to keep the | |||
# docker tags more readable. | |||
VCPKG="943c5ef1c8f6b5e6ced092b242c8299caae2ff01" # 2024.04.26 Release | |||
VCPKG="f7423ee180c4b7f40d43402c2feb3859161ef625" # 2024.06.15 Release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VCPKG="f7423ee180c4b7f40d43402c2feb3859161ef625" # 2024.06.15 Release | |
VCPKG="f7423ee180c4b7f40d43402c2feb3859161ef625" # 2024.06.15 Release |
@@ -1338,6 +1338,7 @@ services: | |||
build: | |||
args: | |||
base: ${REPO}:python-wheel-windows-test-vs2019-base-${PYTHON_WHEEL_WINDOWS_TEST_IMAGE_REVISION} | |||
llvm: 18 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this?
@github-actions crossbow submit -g wheel |
Revision: e77fae5 Submitted crossbow builds: ursacomputing/crossbow @ actions-f3a96f0968 |
Rationale for this change
#37848 upgraded the JIT compiler for LLVM/Gandiva code which presented linking errors with newer version of LLVM. Some Gandiva tests were disabled, and here at Dremio I am running into the same linking problem when trying to build with an updated Arrow library. After reading some threads on the LLVM discord server it appears that updating to llvm 18.1 will fix the symbol issue. I tested locally and was able to re-enable the disabled java tests which were showing the unexported orc symbol issue.
More discussion in apache/arrow-java#63.
What changes are included in this PR?
Updating vcpkg and pinning llvm to 18.1 Notably I found encountered some build problems using the newest vcpkg update, which appeared to be related to the updated grpc libraries. My arrow jar CI build was timing out in this case with no clear error in the logs. The vcpkg vesion included here has the llvm 18 update but not the grpc update (which isn't needed for this issue).
Are these changes tested?
Covered by existing tests. Will also reenable the disabled java tests in a future change.
Are there any user-facing changes?
No.