mirror of https://github.com/hyperledger/besu
Treat output length as a maximum length for CALL operations (#236)
* Fix corner case where Memory did not clear target destination if the new bytes to set was empty. * Use BytesValue.EMPTY instead of Bytes32.EMPTY to make it clear that it's a 0 length BytesValues rather than 32 bytes of zeross. * Treat outputLength for call operations as a maximum length - when the actual data to output is shorter than outputLength, do not zero out the tail end of the memory range. Signed-off-by: Adrian Sutton <adrian.sutton@consensys.net>pull/2/head
parent
8380254edd
commit
b18c9ccdc0
Loading…
Reference in new issue