Raise the limit on locals and stack
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No files or tests are named. Start by locating the JIT checks or constants governing local and stack-variable limits, then compare them with the limits relevant to nodeos. Done means the JIT no longer fails solely because those limits are reached, while nodeos compatibility remains intact.
Written by the indexing model from the issue text.
Description
jit will currently fail if there are too many locals or stack variables. nodeos cannot hit this because the limits are higher than nodeos' limits.
- Dominant language
- C++
- Stars
- 198
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from EOSIO/eos-vm
-
NOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
NOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
NoneOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
HOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
llvm/offload-test-suite#1703 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
BGI-shenzhen/PopLDdecay#25 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
eic/TimeframeBuilder#102 ·