core/vm: use uint256 in EVM implementation (#20787)
* core/vm: use fixed uint256 library instead of big
* core/vm: remove intpools
* core/vm: upgrade uint256, fixes uint256.NewFromBig
* core/vm: use uint256.Int by value in Stack
* core/vm: upgrade uint256 to v1.0.0
* core/vm: don't preallocate space for 1024 stack items (only 16)
Co-authored-by:
Martin Holst Swende <martin@swende.se>
# Conflicts:
# core/vm/common.go
# core/vm/contract.go
# core/vm/eips.go
# core/vm/evm.go
# core/vm/gas_table.go
# core/vm/instructions.go
# core/vm/instructions_test.go
# core/vm/interpreter.go
# core/vm/logger.go
# core/vm/logger_json.go
# core/vm/logger_test.go
# core/vm/stack/stack.go
# go.mod
# go.sum
Showing
- core/vm/eips.go 2 additions, 2 deletionscore/vm/eips.go
- core/vm/gas_table.go 0 additions, 1 deletioncore/vm/gas_table.go
- core/vm/instructions.go 147 additions, 97 deletionscore/vm/instructions.go
- core/vm/instructions_test.go 47 additions, 6 deletionscore/vm/instructions_test.go
- core/vm/interpreter.go 0 additions, 1 deletioncore/vm/interpreter.go
- core/vm/logger.go 5 additions, 5 deletionscore/vm/logger.go
- core/vm/logger_json.go 6 additions, 4 deletionscore/vm/logger_json.go
- core/vm/logger_test.go 2 additions, 2 deletionscore/vm/logger_test.go
- core/vm/stack/stack.go 18 additions, 16 deletionscore/vm/stack/stack.go
Loading
Please register or sign in to comment