Paweł Bylica
Paweł Bylica
I believe this was done in https://github.com/ipsilon/evmone/pull/1233.
Seems no performance regressions: Zen2, clang-18: ``` baseline/execute/main/blake2b_huff/empty_mean +0.0013 +0.0013 10 10 10 10 baseline/execute/main/blake2b_huff/8415nulls_mean -0.0105 -0.0105 603 597 603 597 baseline/execute/main/blake2b_shifts/8415nulls_mean -0.0268 -0.0268 5650 5498 5650 5498 baseline/execute/main/sha1_divs/empty_mean -0.0080...
Maybe this is sometimes faster, but not needed for correctness, so let's skip it.
Something worth taking look at because I got similar error from clang analyzer. However, you should be able to build it without "warnings as errors". What is your cmake invocation?
I planned to take a look directly, but I didn't have time so far. There seems to be multiple issues: 1. This seems to be an false positive, I've reported...
I figured out at least CMake configuration. This should allow building with GCC 15: https://github.com/ipsilon/evmone/pull/1351. The warnings are still present, but the build will progress.
I used this locally with clang-22 (WIP) without any build failures.
@bhartnett, No, currently precompiles are not a part of the evmone shared library. Low level code is in the `evmone::precompiles` static library, but the high level code is in `evmone::state`...
There is not much logic to this. This flag is needed because the EIP-7702 has special handling of precompiles. I.e. we use this flag only not to execute a precompile...
I don't think you will be able to support EVMC VMs with iterative approach. This was mostly a brain dump. But this is a way to have recursive approach without...