-
Notifications
You must be signed in to change notification settings - Fork 11
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
[Testing] Update ROOT and Cling to LLVM18 #209
[Testing] Update ROOT and Cling to LLVM18 #209
Conversation
please test for CMSSW_14_1_ROOT6_X
|
This PR touches too many files (6364 >= 3001) and will not be processed. |
😱 |
FYI, cms-sw/cms-bot#2323 disables the check on the number of files in non-cmssw repositories, so that we can move forward with the testing |
A new Pull Request was created by @aandvalenzuela for branch cms/master/9e38588b80. @aandvalenzuela, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
please test for CMSSW_14_2_ROOT6_X |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b2e919/41168/summary.html Comparison SummarySummary:
|
Pull request #209 was updated. |
cms-bot internal usage |
please test for CMSSW_14_2_ROOT6_X |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b2e919/41185/summary.html Comparison SummarySummary:
|
please test for CMSSW_14_2_ROOT6_X/el8_aarch64_gcc12 |
Matching the change in: - llvm/llvm-project#78463
- Include `StringExtras.h` This is now needed due to: llvm/llvm-project@3ff3af3
In LLVM 18 with incremental extensions enabled, the Preprocessor will never report tok::eof, but tok::annot_repl_input_end instead.
Prevents failures such as: ``` Processing roottest/root/meta/runnamespace.C... Error in cling::MetaProcessor: cannot read from binary input: 'runnamespace.C' ``` This is needed for macros that start with `{` after the rebase
C++20 builds were failing due to the commit: llvm-project/commit/574ee1c02ef73b66c5957cf93888234b0471695f with an error `imported non C++20 importable modules`
This makes them run after the <Platform> library: It provides the __cxa_atexit function, which must not be found in the process.
LLVM now defines multiple Dylibs, and __cxa_atexit is provided in the <Platform> library.
We started seeing an assertion failure in ~FinalizedAlloc when we moved the generators to ProcessSymbols JITDylib: [cling] Move generators to ProcessSymbols JITDylib This ikely changed the destruction order that caused the assertion to trigger.
This fixes the Cling test Driver/E.C.
This applies the upstream changes in commit llvm/llvm-project@9992b38 to a copy of the modulemap from MacOSX14.2.sdk.
This fixes the failing python enum tests like: - `roottest-python-cpp-cpp` - `roottest-python-cmdLineUtils-ROOT_8197` Also remove `R__BYTESWAP` which should not be needed anymore. The leak was fixed with: llvm/llvm-project#78311 This caused our tests to fail as they relied on the previous behavior.
Upstream LLVM now unconditionally uses indirect / PC relative personality encodings since commit llvm/llvm-project@ca65969 This leads to references of DW.ref.__gxx_personality_v0 that cannot be resolved with RuntimeDyld, that we are still using for the moment. As a fix, auto-claim symbols as we are doing for PPC, see upstream commit: llvm/llvm-project@72ea1a7
There are still failures with RuntimeDyld on AArch64 which seem to be solved with JITLink, so make the switch now.
3873f4d
to
a52d34d
Compare
Pull request #209 was updated. |
cms-bot internal usage |
Testing ROOT llvm18 update as requested in root-project#15696 (comment)