-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[runtime_cxxmodules] Enable on AArch64 #16401
[runtime_cxxmodules] Enable on AArch64 #16401
Conversation
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.
LGTM! Thank you!
Test Results 18 files 18 suites 4d 2h 21m 3s ⏱️ Results for commit b012169. ♻️ This comment has been updated with latest results. |
I propose to merge it once we have the ARM nodes online to be able to test immediately, would this be ok? |
Yes, I'm waiting for the AArch64 node in our CI so we can test there, and then (after) I'd still like to ask CMS to run their tests. |
632b085
to
3320cc2
Compare
@aandvalenzuela @smuzaffar if you have some cycles, can you test this change with CMSSW on AArch64? This should align the configurations with x86_64 to also enable |
cms-sw#212 is running cmssw aarch64 tests |
Hi, most of cmssw tests passed but for few relvals we get runtime errors like [a]
|
Thanks for testing! This needs debugging (likely after CHEP)... |
3320cc2
to
473c7b2
Compare
Revisiting this PR before the end of the year: Thanks to the clear error message and some guess work, I managed to reproduce the issue in a standalone ROOT session:
Currently still investigating why this happens with |
473c7b2
to
3c3c8c1
Compare
Alright, the issue with the reproducer in #16401 (comment) is understood and fixed. Let's hope that this is also fixes the CMS relvals - @aandvalenzuela @smuzaffar could you maybe run the tests again? Thanks in advance for all your help! |
cmssw tests started via cms-sw#215 |
In case of weak definitions, JITLink might merge symbols because we currently add all llvm::Module's into a single JITDylib. For merges that late in the pipeline, we also have to prevent optimizations that take advantage of "localness" to avoid out-of-range relocations for example on AArch64.
It was disabled in commit a67863d ("Disable modules on aarch64 due to ODR violation") in 2019. I cannot reproduce these problems on lxplus-arm, so try to turn it back on.
cmssw tests for aarch64 look good |
Fantastic, thank you! Unfortunately our macOS nodes are not happy, so I'll need to push a slightly fixed version. I don't think we strictly need to test with full CMSSW once more... |
3c3c8c1
to
b012169
Compare
@vgvassilev FYI you already approved this three months ago, and now that the issue in CMS is fixed I plan to land this soon |
Go ahead. |
It was disabled in commit a67863d ("Disable modules on aarch64 due to ODR violation") in 2019. I cannot reproduce these problems on
lxplus-arm
, so try to turn it back on.