Don't allow multiple copies of the same array on device
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- C
- Stars
- 17
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We shouldn't allow the same array to be mapped with two different sets of
indices for now. i.e.,
nomp_update(a, 0, 10, sizeof(double), NOMP_TO);
nomp_update(a, 2, 8, sizeof(double), NOMP_TO);
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the nomp_update entry point and the device-array mapping logic. Trace how existing mappings are recorded, then verify that mapping the same array with different index sets is rejected, including the two ranges shown in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100