oneapi-src / oneapi-src/unified-memory-framework
add valgrind instrumentation
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 98
- Forks
- 48
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 6
Description
currently, our valgrind instrumentation is empty:
#define VALGRIND_DO_MEMPOOL_ALLOC(pool, ptr, size) \
do { \
(void)(pool); \
(void)(ptr); \
(void)(size); \
} while (0)
#define VALGRIND_DO_MEMPOOL_FREE(pool, ptr) \
do { \
(void)(pool); \
(void)(ptr); \
} while (0)
#endif
additionally, our GPU workflows should be run with all instrumentation enabled (could be done in Nightly builds)
Contributor guide
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
Locate the VALGRIND_DO_MEMPOOL_ALLOC and VALGRIND_DO_MEMPOOL_FREE macro definitions and identify the GPU workflow configuration. Start by checking how instrumentation is currently disabled, then verify that the macros perform the intended Valgrind mempool operations and that GPU workflows run with instrumentation enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100