[QST] Why tma_load.get_slice(0) here always need 0?
Open
Nobody has claimed this yet.
? - Needs Triage
inactive-30d
inactive-90d
question
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
What is your question?
I see many cases with this get_slice(0), I am not sure, does this mean only thread 0 to do the work? In that case, this must always 0 for TMA?
Thanks!
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 with the screenshot and the occurrences of tma_load.get_slice(0) referenced in the issue. Trace what get_slice(0) represents in the surrounding TMA usage, then document whether the zero is tied to thread 0 and whether it is required for TMA. There are no file or test paths specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100