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
[BuildRules] Disable LTO flags for ROCM products #8291
Conversation
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_13_0_X/master. @cmsbuild, @smuzaffar, @aandvalenzuela, @iarspider can you please review it and eventually sign? Thanks. |
test parameters:
|
please test |
Most likely we can - but I'm not sure if we should. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-38b7c6/30416/summary.html Comparison SummarySummary:
|
please test for CMSSW_13_0_LTO_X |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-38b7c6/30432/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see more details here: |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_13_0_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
I think problem is mixing LTO objects build with llvm (hipcc) and gcc. For now lets disable LTO for rocm products. I will check if for rocm products ( where .hip.cc files exists) we can compile default
.cc
files with llvm instead ofgcc