Alex Beregszaszi

> set_option is part of evmc, and moving it to evmone will probably break stuff, right? Btw, are you sure you are using latest master? In latest master there's an...

> And this is a big problem for languages who manage their memory differently I know the pain with Rust, at least it has boxes to solve it. We were...

@chfast so should just `execute` and `baseline_execute` be exported as the quick solution?

Since I see the `proof_systems` module already supports BLS12-381, the only remaining task here is adding it to `SolidityCompatibleSchemes` and providing a verifier in Solidity. So it seems after all...

Perhaps this shouldn't be an optimiser step, but rather an analyzer warning: "Side-effect free statement."

It seems that an old version of llvm always included a linker custom section and the `milestone1` version of sentinel was probably compiled like that. Source: https://github.com/WebAssembly/wabt/issues/842 Manually dropping all...

Bummer, this needs `python` in the build env: ``` [10/106] Generating WasmIntrinsics.cpp FAILED: src/passes/WasmIntrinsics.cpp cd /home/builder/build/deps/src/binaryen-build/src/passes && python /home/builder/build/deps/src/binaryen/scripts/embedwast.py /home/builder/build/deps/src/binaryen/src/passes/wasm-intrinsics.wast /home/builder/build/deps/src/binaryen-build/src/passes/WasmIntrinsics.cpp /bin/sh: 1: python: not found ```

Our immediate benefit is the arguments to `callExport` are const so we can simplify that code, however two actual reasons: - wanted to pull in fixes from the last 3...

After supplying python, this still has some weird build issue: ``` 100%] Linking CXX executable bin/wasm-emscripten-finalize CMakeFiles/wasm-emscripten-finalize.dir/src/tools/wasm-emscripten-finalize.cpp.o: In function `main': wasm-emscripten-finalize.cpp:(.text+0x111b): undefined reference to `wasm::ModuleReader::read(std::__cxx11::basic_string, wasm::Module&, std::__cxx11::basic_string)' clang: error: linker...

Rebased on top the toolchain file, but still failing.