RoaringBitmap / RoaringBitmap/CRoaring
Investigate using __vectorcall under Windows
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 334
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 17
Description
It is possible that we might be able to improve our performance by marking some functions under Windows with __vectorcall so that they use a better calling convention.
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
No files, functions, tests, or benchmarks are named. Start by locating the Windows-specific C functions and the project's performance benchmark setup; done requires a measured determination of whether __vectorcall improves performance and a clearly scoped follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100