-
Notifications
You must be signed in to change notification settings - Fork 4.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
Do not include EventSetup record definitions in device code #44828
Do not include EventSetup record definitions in device code #44828
Conversation
type bugfix |
enable gpu |
please test |
cms-bot internal usage |
type pf |
I forgot about it ! |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44828/40070
|
A new Pull Request was created by @fwyzard for master. It involves the following packages:
@mandrenguyen, @jfernan2 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3a17e7/39046/summary.html Comparison SummarySummary:
GPU Comparison SummarySummary:
|
This PR looks fine from RECO side, but I wonder if we should move to #44682 to consider the comments and extra changes reflected there |
These two PRs are effectively identical. |
-1 |
PR description:
Do not include
EventSetup
record definitions in device code.To minimise the code changes, forward-declare the records in a common header, and include their definition only in host code.
PR validation:
Builds on top of CMSSW_14_1_X_2024-04-23-2300.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
A backport is not required, though it may be prepared to keep the 14.0.x and 14.1.x alpaka code base consistent.