[SBIN] Define and implement symbol visibility controls in cuvs_c
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
This requires implementing mechanisms within the cuvs_c library to control which symbols (functions and variables) are publicly visible when the library is compiled.
In short we want to compile all the C library object files with -fvisibility=hidden and explicitly control the symbols we expose maybe best done via CUVS_C_API_BEGIN / END macros that we can place in the file that evaluate to #pragma GCC visibility push(default) macros
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
Start by locating the cuvs_c library build configuration and its public C headers. Review how the library is compiled and where CUVS_C_API_BEGIN/END could apply. Done means object files use hidden visibility while the intended public functions and variables remain exposed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend-api-design, build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100