runtimeverification / runtimeverification/haskell-backend
kore-exec profile: why are there so many calls to prove?
Open
Nobody has claimed this yet.
investigation
needs-reproducing
performance
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
This profile comes from #2757, on a 2-character input string. The proof takes ~800ms.
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 reading issue #2757 to understand the two-character proof, then inspect the attached valid-jump-dests.json profile data. Trace which proof steps account for the many calls to prove and determine why the run takes about 800ms. Done means explaining the call volume and identifying a concrete direction for reducing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100