Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
SDL::modulesBuffer as an ES product #16
SDL::modulesBuffer as an ES product #16
Changes from all commits
5aa6223
efec09f
7942f33
cbfc1aa
7b50c1b
dd468e3
f3bbe84
473d09e
55c3a80
c4e0dac
ebb3001
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The
ComponentName
is strictly speaking redundant, because the framework already provides the same functionality out of the box withappendToDataLabel
parameter.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.
Hi @makortel
Is there a way to avoid having an explicit host-specific RecoTracker/LST/src/ES_ModulesDev.cc ?
For some reason this
TEMPLATED_DATA_REG
leads to appropriate symbols inlibRecoTrackerLSTCudaAsync.so
, but nothing in thelibRecoTrackerLSTSerialSync.so
This behavior doesn't change if I remove
RecoTracker/LST/src/ES_ModulesDev.cc
.Can LTO be at play in some way?
I tried to add
<flags CXXFLAGS="-fno-lto"/>
, but it didn't make the CPU ESedm::typelookup::className
symbols show up in the CPU/serial so file.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.
No, the behavior is intentional (at least for now). We want the non-Alpaka modules to be able to consume the host-side EventSetup data products (analogously to host-side Event data products). From there it follows that the symbols of the host-side data products must be in the non-Alpaka library of
RecoTracker/LST
, and the.cc
file containing theTYPELOOKUP_DATA_REG()
for the host-specific data product must reside there.