microsoft / microsoft/snmalloc
Examine hardened compiler performance impact.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2k
- Forks
- 138
- Avg merge
- 11h 19m
- Merged PRs (30d)
- 5
Description
#818 also reminds me of another thing: some clang distribution may enable things like -ftrivial-auto-var-init=pattern (and -fstrong-stack-protector) enabled by default, we may want to examine the performance impact and opt out such hardening from the routines where they may cause performance issue.
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 by reviewing issue #818 and the compiler configurations that enable -ftrivial-auto-var-init=pattern or -fstrong-stack-protector. Identify the affected allocator routines, measure their performance impact, and report which hardening options, if any, warrant scoped opt-outs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100