Experiment: do not llvm kompile, evaluate static data lookups in HS backend #853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Evaluates the static data lookup functions using the Haskell backend evaluator only.
The lookup functions are annotated with
no-evaluatorsso they are never sent to the LLVM backend library for evaluation. Default equations are generated together with the defining equations from the SMIR JSON data.kmir prove-rs, the prover uploads an extra module (manually) with the lookup function equations. Unfortunately, this requires us to also use the prover'sextra_moduleoption to ensure that the equations are in scope for the proof.KMIR.from_kompiled_kore(..., symbolic=True)only appends to the Haskelldefinition.kore, and uses the unmodified LLVM library. All clients offrom_kompiled_korewill use the new HS-only evaluation automatically.kmir section-edgeusesKMIR.from_kompiled_kore(..., symbolic=True)kmir run --haskell-backendusesKMIR.from_kompiled_kore(..., symbolic=True)kmir runwithout--haskell-backend, we still invokellvm-kompile(withinKMIR.from_kompiled_kore(..., symbolic=False)and use the LLVM interpreter with the lookup function equations included.