GPU stacktrace
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 49
- Forks
- 9
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 1
Description
Don't know how this feasible, but it would be useful to recover a stacktrace from a function called from a GPU device in https://github.com/GEOS-DEV/LvArray/blob/bc43fa5f76174475e2f3f9af706e379350779244/src/Macros.hpp#L149
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 src/Macros.hpp around line 149 and inspect how functions called from GPU device code are defined or wrapped. Determine whether the supported GPU toolchains expose a recoverable device stacktrace and identify the portability constraints. Done means documenting a feasible approach or establishing that this cannot be supported across the project's target environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100