[ ] We need to cast pointers safely from i256 to register size ints when calling into runtime API methods. While in theory all pointers should be automatically in bounds, this assumption doesn't necessarily hold (as pointers / memory offsets are potentially untrusted user input). Safe truncation adds a lot of overhead in contract code; I tried to offload it into it's own function but on 32bit PolkaVM leads to even more code overall (because we have an i256 argument). On 64bit this could work though and if so we should use this optimization when compiling for size (-Oz).
[ ] zbb instructions need to be implemented in PolkaVM. By experimentally switching the LLVM target to rv64 with+zbb significant changes in code size can be observed:
---- cases::tests::codesize stdout ----
ERC20: 93072 bytes (change from 194140 bytes)
Baseline: 63128 bytes (change from 131084 bytes)
Flipper: 63688 bytes (change from 131796 bytes)
Fibonacci: 63880 bytes (change from 133328 bytes)
Computation: 65056 bytes (change from 135456 bytes)
[ ] Investigate potential improvements of byte swaps, memset, memmove, mulmod, divs and the like
[ ] Check all alignments, attributes etc. if they still make sense with our target
[ ] When passing pointers, the runtime could issue sbrk instead of trapping for OOB memory accesses.
-Oz).zbbinstructions need to be implemented in PolkaVM. By experimentally switching the LLVM target to rv64 with+zbbsignificant changes in code size can be observed:sbrkinstead of trapping for OOB memory accesses.