Implement optimization pass to make variable scopes as tight as possible
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 160
- Forks
- 59
- Avg merge
- 21h 45m
- Merged PRs (30d)
- 26
Description
The idea is to automatically determine when variables can go out of scope because they are no longer needed. (Relying on a live variables analysis.)
There is another question here: does this optimization buy us anything or does clang or gcc already do this for us automatically?
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 file or test is named; start by locating the live variables analysis and reviewing how variable scopes are represented in the compiler. Check whether clang or gcc already provide the proposed optimization, then define and validate the pass only if it provides a measurable benefit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100