2021-05-20 09:15:00 +00:00
|
|
|
# Nimbus - Binary compatibility on the host side of the EVMC API interface
|
|
|
|
#
|
|
|
|
# Copyright (c) 2019-2021 Status Research & Development GmbH
|
|
|
|
# Licensed under either of
|
|
|
|
# * Apache License, version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
|
|
|
|
# * MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)
|
|
|
|
# at your option. This file may not be copied, modified, or distributed except according to those terms.
|
|
|
|
|
|
|
|
#{.push raises: [Defect].}
|
|
|
|
|
|
|
|
when not declaredInScope(included_from_host_services):
|
|
|
|
{.error: "Do not import this file directly, import host_services instead".}
|
|
|
|
|
|
|
|
import evmc/evmc
|
|
|
|
|
|
|
|
template toHost(p: evmc_host_context): TransactionHost =
|
|
|
|
cast[TransactionHost](p)
|
|
|
|
|
|
|
|
proc accountExists(p: evmc_host_context, address: var evmc_address): c99bool {.cdecl.} =
|
|
|
|
toHost(p).accountExists(address.fromEvmc)
|
|
|
|
|
|
|
|
proc getStorage(p: evmc_host_context, address: var evmc_address,
|
|
|
|
key: var evmc_bytes32): evmc_bytes32 {.cdecl.} =
|
|
|
|
toHost(p).getStorage(address.fromEvmc, key.fromEvmc).toEvmc
|
|
|
|
|
|
|
|
proc setStorage(p: evmc_host_context, address: var evmc_address,
|
|
|
|
key, value: var evmc_bytes32): evmc_storage_status {.cdecl.} =
|
|
|
|
toHost(p).setStorage(address.fromEvmc, key.fromEvmc, value.fromEvmc)
|
|
|
|
|
|
|
|
proc getBalance(p: evmc_host_context,
|
|
|
|
address: var evmc_address): evmc_uint256be {.cdecl.} =
|
|
|
|
toHost(p).getBalance(address.fromEvmc).toEvmc
|
|
|
|
|
|
|
|
proc getCodeSize(p: evmc_host_context,
|
|
|
|
address: var evmc_address): csize_t {.cdecl.} =
|
|
|
|
toHost(p).getCodeSize(address.fromEvmc)
|
|
|
|
|
|
|
|
proc getCodeHash(p: evmc_host_context,
|
|
|
|
address: var evmc_address): evmc_bytes32 {.cdecl.} =
|
|
|
|
toHost(p).getCodeHash(address.fromEvmc).toEvmc
|
|
|
|
|
|
|
|
proc copyCode(p: evmc_host_context, address: var evmc_address, code_offset: csize_t,
|
|
|
|
buffer_data: ptr byte, buffer_size: csize_t): csize_t {.cdecl.} =
|
|
|
|
toHost(p).copyCode(address.fromEvmc, code_offset, buffer_data, buffer_size)
|
|
|
|
|
|
|
|
proc selfDestruct(p: evmc_host_context, address,
|
|
|
|
beneficiary: var evmc_address) {.cdecl.} =
|
|
|
|
toHost(p).selfDestruct(address.fromEvmc, beneficiary.fromEvmc)
|
|
|
|
|
|
|
|
proc call(p: evmc_host_context, msg: var evmc_message): evmc_result {.cdecl.} =
|
|
|
|
toHost(p).call(msg)
|
|
|
|
|
|
|
|
proc getTxContext(p: evmc_host_context): evmc_tx_context {.cdecl.} =
|
|
|
|
toHost(p).getTxContext()
|
|
|
|
|
|
|
|
proc getBlockHash(p: evmc_host_context, number: int64): evmc_bytes32 {.cdecl.} =
|
|
|
|
# TODO: `HostBlockNumber` is 256-bit unsigned. It should be changed to match
|
|
|
|
# EVMC which is more sensible.
|
|
|
|
toHost(p).getBlockHash(number.uint64.u256).toEvmc
|
|
|
|
|
|
|
|
proc emitLog(p: evmc_host_context, address: var evmc_address,
|
|
|
|
data: ptr byte, data_size: csize_t,
|
|
|
|
topics: ptr evmc_bytes32, topics_count: csize_t) {.cdecl.} =
|
|
|
|
toHost(p).emitLog(address.fromEvmc, data, data_size,
|
|
|
|
cast[ptr HostTopic](topics), topics_count)
|
|
|
|
|
2021-08-05 01:52:40 +00:00
|
|
|
proc accessAccount(p: evmc_host_context,
|
|
|
|
address: var evmc_address): evmc_access_status {.cdecl.} =
|
|
|
|
toHost(p).accessAccount(address.fromEvmc)
|
|
|
|
|
|
|
|
proc accessStorage(p: evmc_host_context, address: var evmc_address,
|
|
|
|
key: var evmc_bytes32): evmc_access_status {.cdecl.} =
|
|
|
|
toHost(p).accessStorage(address.fromEvmc, key.fromEvmc)
|
|
|
|
|
2021-08-09 16:38:59 +00:00
|
|
|
let hostInterface = evmc_host_interface(
|
|
|
|
account_exists: accountExists,
|
|
|
|
get_storage: getStorage,
|
|
|
|
set_storage: setStorage,
|
|
|
|
get_balance: getBalance,
|
|
|
|
get_code_size: getCodeSize,
|
|
|
|
get_code_hash: getCodeHash,
|
|
|
|
copy_code: copyCode,
|
|
|
|
selfdestruct: selfDestruct,
|
|
|
|
call: call,
|
|
|
|
get_tx_context: getTxContext,
|
|
|
|
get_block_hash: getBlockHash,
|
|
|
|
emit_log: emitLog,
|
|
|
|
access_account: accessAccount,
|
|
|
|
access_storage: accessStorage,
|
|
|
|
)
|
2021-05-20 09:15:00 +00:00
|
|
|
|
|
|
|
# The built-in Nimbus EVM, via imported C function.
|
|
|
|
proc evmc_create_nimbus_evm(): ptr evmc_vm {.cdecl, importc.}
|
|
|
|
|
2021-06-07 14:20:13 +00:00
|
|
|
# Pull in the definition of the above function because we're not building it as
|
|
|
|
# a separate library yet.
|
|
|
|
import ./evmc_vm_glue
|
|
|
|
|
EVMC: Improve host call tracing and fix nested call C stack usage
This combines two things, a C stack usage change with EVM nested calls
via EVMC, and changes to host call tracing.
Feature-wise, the tracing is improved:
- Storage keys and values are make more sense.
- The message/result/context objects are shown with all relevant fields.
- `call` trace is split into entry/exit, so these can be shown around the
called contract's operations, instead of only showing the `call` parameters
after the nested call is finished.
- Nested calls are indented, which helps to highlight the flow.
- C stack usage considerably reduced in nested calls when more functionality
is enabled (either tracing here, or other things to come).
This will seem like a minor patch, but C stack usage was the real motivation,
after plenty of time in the debugger.
Nobody cares about stack when `showTxCalls` (you can just use a big stack when
debugging). But these subtle changes around the `call` path were found to be
necessary for passing all tests when the EVMC nested call code is completed,
and that's a prerequisite for many things: async EVM, dynamic EVM, Beam Sync,
and to fix https://github.com/status-im/nimbus-eth1/issues/345.
Signed-off-by: Jamie Lokier <jamie@shareable.org>
2021-08-09 14:54:38 +00:00
|
|
|
proc evmcExecComputation*(host: TransactionHost): EvmcResult {.inline.} =
|
|
|
|
host.showCallEntry(host.msg)
|
|
|
|
|
2021-05-20 09:15:00 +00:00
|
|
|
let vm = evmc_create_nimbus_evm()
|
|
|
|
if vm.isNil:
|
|
|
|
echo "Warning: No EVM"
|
|
|
|
# Nim defaults are fine for all other fields in the result object.
|
EVMC: Improve host call tracing and fix nested call C stack usage
This combines two things, a C stack usage change with EVM nested calls
via EVMC, and changes to host call tracing.
Feature-wise, the tracing is improved:
- Storage keys and values are make more sense.
- The message/result/context objects are shown with all relevant fields.
- `call` trace is split into entry/exit, so these can be shown around the
called contract's operations, instead of only showing the `call` parameters
after the nested call is finished.
- Nested calls are indented, which helps to highlight the flow.
- C stack usage considerably reduced in nested calls when more functionality
is enabled (either tracing here, or other things to come).
This will seem like a minor patch, but C stack usage was the real motivation,
after plenty of time in the debugger.
Nobody cares about stack when `showTxCalls` (you can just use a big stack when
debugging). But these subtle changes around the `call` path were found to be
necessary for passing all tests when the EVMC nested call code is completed,
and that's a prerequisite for many things: async EVM, dynamic EVM, Beam Sync,
and to fix https://github.com/status-im/nimbus-eth1/issues/345.
Signed-off-by: Jamie Lokier <jamie@shareable.org>
2021-08-09 14:54:38 +00:00
|
|
|
result = EvmcResult(status_code: EVMC_INTERNAL_ERROR)
|
|
|
|
host.showCallReturn(result)
|
|
|
|
return
|
2021-05-20 09:15:00 +00:00
|
|
|
|
|
|
|
let hostContext = cast[evmc_host_context](host)
|
2021-08-17 16:18:07 +00:00
|
|
|
host.hostInterface = hostInterface.unsafeAddr
|
2021-05-20 09:15:00 +00:00
|
|
|
|
|
|
|
# Without `{.gcsafe.}:` here, the call via `vm.execute` results in a Nim
|
|
|
|
# compile-time error in a far away function. Starting here, a cascade of
|
|
|
|
# warnings takes place: "Warning: '...' is not GC-safe as it performs an
|
|
|
|
# indirect call here [GCUnsafe2]", then a list of "Warning: '...' is not
|
|
|
|
# GC-safe as it calls '...'" at each function up the call stack, to a high
|
|
|
|
# level function `persistBlocks` where it terminates compilation as an error
|
|
|
|
# instead of a warning.
|
|
|
|
#
|
|
|
|
# It is tempting to annotate all EVMC API functions with `{.cdecl, gcsafe.}`,
|
|
|
|
# overriding the function signatures from the Nim EVMC module. Perhaps we
|
|
|
|
# will do that, though it's conceptually dubious, as the two sides of the
|
|
|
|
# EVMC ABI live in different GC worlds (when loaded as a shared library with
|
|
|
|
# its own Nim runtime), very similar to calling between threads.
|
|
|
|
#
|
|
|
|
# TODO: But wait: Why does the Nim EVMC test program compile fine without
|
|
|
|
# any `gcsafe`, even with `--threads:on`?
|
|
|
|
{.gcsafe.}:
|
2021-08-09 16:38:59 +00:00
|
|
|
result = vm.execute(vm, hostInterface.unsafeAddr, hostContext,
|
EVMC: Improve host call tracing and fix nested call C stack usage
This combines two things, a C stack usage change with EVM nested calls
via EVMC, and changes to host call tracing.
Feature-wise, the tracing is improved:
- Storage keys and values are make more sense.
- The message/result/context objects are shown with all relevant fields.
- `call` trace is split into entry/exit, so these can be shown around the
called contract's operations, instead of only showing the `call` parameters
after the nested call is finished.
- Nested calls are indented, which helps to highlight the flow.
- C stack usage considerably reduced in nested calls when more functionality
is enabled (either tracing here, or other things to come).
This will seem like a minor patch, but C stack usage was the real motivation,
after plenty of time in the debugger.
Nobody cares about stack when `showTxCalls` (you can just use a big stack when
debugging). But these subtle changes around the `call` path were found to be
necessary for passing all tests when the EVMC nested call code is completed,
and that's a prerequisite for many things: async EVM, dynamic EVM, Beam Sync,
and to fix https://github.com/status-im/nimbus-eth1/issues/345.
Signed-off-by: Jamie Lokier <jamie@shareable.org>
2021-08-09 14:54:38 +00:00
|
|
|
evmc_revision(host.vmState.fork), host.msg,
|
|
|
|
if host.code.len > 0: host.code[0].unsafeAddr else: nil,
|
|
|
|
host.code.len.csize_t)
|
2021-05-24 17:00:38 +00:00
|
|
|
|
EVMC: Improve host call tracing and fix nested call C stack usage
This combines two things, a C stack usage change with EVM nested calls
via EVMC, and changes to host call tracing.
Feature-wise, the tracing is improved:
- Storage keys and values are make more sense.
- The message/result/context objects are shown with all relevant fields.
- `call` trace is split into entry/exit, so these can be shown around the
called contract's operations, instead of only showing the `call` parameters
after the nested call is finished.
- Nested calls are indented, which helps to highlight the flow.
- C stack usage considerably reduced in nested calls when more functionality
is enabled (either tracing here, or other things to come).
This will seem like a minor patch, but C stack usage was the real motivation,
after plenty of time in the debugger.
Nobody cares about stack when `showTxCalls` (you can just use a big stack when
debugging). But these subtle changes around the `call` path were found to be
necessary for passing all tests when the EVMC nested call code is completed,
and that's a prerequisite for many things: async EVM, dynamic EVM, Beam Sync,
and to fix https://github.com/status-im/nimbus-eth1/issues/345.
Signed-off-by: Jamie Lokier <jamie@shareable.org>
2021-08-09 14:54:38 +00:00
|
|
|
host.showCallReturn(result)
|