when a shard locks a write scope that should be sufficient to retire transactions that require that scope as read

Use correct preprocessor define (__arm__ vs __ARM__) to detect compilation for ARM architecture CPUs.

Allocate 512MB of address-space instead of 1GB for memory objects on 32-bit. This allows the test scripts to have more than one around at a time without exhausting 2GB of user address-space.

Fix crash when deleting a partially initialized MemoryInstance after its address-space allocation fails

Explicitly trap on (INT_MIN / -1) to ensure LLVM DCE or constant folding doesn't eliminate the trap.

WASM globals are disparate from WASM linear memory. Similar to how we reset linear memory after each invocation, we need to reset globals as well.

to mongo_db_plugin. #1047

support in chain_controller constructor.
Hookup mongo_db_plugin to applied_irreversible_block signal.
Add wipe database calls on resync and replay options. #1047

Linear memory is optional in WASM. Protect against crashes when a WASM doesn't use it.

to mongo_db_plugin. #1047

add abi test for post recovery, pass recovery, veto recovery, set abi, set code, nonce native contract action

properly use the account for read locks in data accesses, rename some "scopes" to locks where appropriate

Previously, the WASM "start" function would be called once right after compilation. This was problematic for two reasons. 1) It was called during a period of time not expected (not during any context), and 2) if the user was expecting the start function to be called for initialization it would not be called after the memory had been reset on subsequent apply() calls -- that could be a surprise.

Now call the WASM "start" function before each init() and apply().