runtimeverification / runtimeverification/evm-semantics

Porting the benchmarks proofs to the haskell backend

Open
#858 1 comment 0 reactions 2 assignees View on GitHub

@ssaha6 is already working on this.

Since Jul 8, 2020.

Dominant language
KCL
Stars
591
Forks
156
Avg merge
2h 19m
Merged PRs (30d)
1

Description

List of the proofs to be ported:

  • tests/specs/benchmarks/address00-spec.k: https://github.com/kframework/evm-semantics/pull/839
  • tests/specs/benchmarks/bytes00-spec.k
  • tests/specs/benchmarks/ecrecover00-siginvalid-spec.k
  • tests/specs/benchmarks/ecrecover00-sigvalid-spec.k
  • tests/specs/benchmarks/ecrecoverloop00-sig0-invalid-spec.k
  • tests/specs/benchmarks/ecrecoverloop00-sig1-invalid-spec.k
  • tests/specs/benchmarks/ecrecoverloop00-sigs-valid-spec.k
  • tests/specs/benchmarks/ecrecoverloop02-sig0-invalid-spec.k
  • tests/specs/benchmarks/ecrecoverloop02-sig1-invalid-spec.k
  • tests/specs/benchmarks/ecrecoverloop02-sigs-valid-spec.k
  • tests/specs/benchmarks/encode_keccak00-spec.k
  • tests/specs/benchmarks/encodepacked_keccak01-spec.k
  • tests/specs/benchmarks/keccak00-spec.k
  • tests/specs/benchmarks/overflow00-nooverflow-spec.k: https://github.com/kframework/evm-semantics/pull/851
  • tests/specs/benchmarks/overflow00-overflow-spec.k: https://github.com/kframework/evm-semantics/pull/851
  • tests/specs/benchmarks/requires01-a0gt0-spec.k
  • tests/specs/benchmarks/requires01-a0le0-spec.k
  • tests/specs/benchmarks/staticarray00-spec.k
  • tests/specs/benchmarks/staticloop00-a0lt10-spec.k
  • tests/specs/benchmarks/storagevar00-spec.k: https://github.com/kframework/evm-semantics/pull/857
  • tests/specs/benchmarks/storagevar01-spec.k: #882
  • tests/specs/benchmarks/storagevar02-nooverflow-spec.k
  • tests/specs/benchmarks/storagevar02-overflow-spec.k: #882
  • tests/specs/benchmarks/storagevar03-spec.k: #882

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.