-
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
RecoTracker/PixelSeeding: array subscript ... is above array bounds in Alpaka/FlexiStorage #45179
Comments
cms-bot internal usage |
A new Issue was created by @iarspider. @antoniovilela, @smuzaffar, @makortel, @rappoccio, @sextonkennedy, @Dr15Jones can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign HeterogeneousCore/AlpakaInterface,RecoTracker/PixelSeeding |
New categories assigned: heterogeneous,reconstruction @fwyzard,@jfernan2,@makortel,@mandrenguyen you have been requested to review this Pull request/Issue and eventually sign? Thanks |
First occurrence in CMSSW_14_1_X_2024-06-05-2300 |
@AdrianoDee |
This is probably not a real issue. [I think I was wrong initially] cmssw/RecoTracker/PixelSeeding/plugins/alpaka/CAHitNtupletGeneratorKernelsImpl.h Lines 552 to 553 in 64d4f3b
with the final line calls
notice the cmssw/HeterogeneousCore/AlpakaInterface/interface/workdivision.h Lines 254 to 255 in 64d4f3b
so the However, looking at the definition of
and
then assuming |
@Dr15Jones thanks for looking into this issue 👍🏻 |
yep. All that was indeed intentional (at least in the CUDA version). |
I have opened #45340 to suppress this error |
One more item, if I add assert(static_cast<decltype(tracks_view.hitIndices().nOnes())>(idx) < tracks_view.hitIndices().nOnes()); right before the call to |
A bit more investigation, if I change the loop condition to actually be on the end, i.e. for (auto idx : cms::alpakatools::uniform_elements(acc, tracks_view.hitIndices().totOnes())) the warning states that the value goes 1 beyond the end, instead of just the end (which is what is actually going on). So the compiler really thinks that |
is this still active after #45455 and cms-sw/cmsdist#9301 ? |
The warning should be fixed (i.e. disabled). I would still like to double check our code and make sure the range is correct, and in case try to write a simpler reproducer to submit to gcc. |
In all IBs, GCC emits the following warnings:
The text was updated successfully, but these errors were encountered: