runtimeverification / runtimeverification/haskell-backend

Set simplification lemmas appear to cause slowdown

Open
#3,693 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
224
Forks
43
PR merge metrics
No merged PRs in 30d

Description

From @PetarMax :
I am not understanding why my lemmas PR is making the Haskell backend CI much slower. I am suspecting it is the set-related lemmas, but they are now minimal and much more concrete:

  // ########################
  // Set Reasoning
  // ########################

    rule S:Set |Set SetItem( X ) => S requires X in S [concrete(X), simplification]

    rule X in S:Set SetItem ( Y ) => true   requires X ==Int Y  [concrete(X, Y), simplification]
    rule X in S:Set SetItem ( Y ) => X in S requires X =/=Int Y [concrete(X, Y), simplification]

and I really would not want to have terms like ((A |Set SetItem (X)) |Set SetItem (Y)) |Set SetItem(X) in my configurations.

We should run an analysis of these simplification lemmas to check what is happening (especially whether and how many times they fail).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked lemmas PR and the Haskell backend CI slowdown. Analyze the three Set simplification lemmas, especially whether they fail and how often; done means explaining their contribution to the slowdown and the observed term growth.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.