Audit ARCH_WORD in jumbo.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Remove things which do not 'need' native machine size for performance. Use uint32_t or uint64_t if there are certain areas which require a specific size.
Alignment usage may need to be looked at for speed for data which actually is handled as 4 byte words. Many places use ARCH_WORD for alignment. We need to see if there is any benefit or not (I bet not). also, going to uint32_t in this cases will save memory space (not huge, but some).
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 reviewing ARCH_WORD uses throughout jumbo and the linked commit discussion. Identify uses that do not require native machine size, replace them with appropriately sized integer types where justified, and assess whether ARCH_WORD-based alignment is beneficial; done when the audit is complete and the relevant size and alignment choices are validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100