continue doesn't produce the same opcodes as in normal gluajit
Open
Nobody has claimed this yet.
bug
- Dominant language
- C
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
it breaks compatibility with undefined behavior in general (cac will detect it as a cheat)
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
Compare the opcode sequence produced for a continue statement by this repository with normal gluajit, focusing on the compatibility difference described in the issue. Reproduce the mismatch and determine the opcode behavior that CAC treats as a cheat; the work is done when continue produces compatible opcodes without that detection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100