You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix high bits stored in uint64 representation of Word
Without first converting to uint32_t, the getters for wasm_val_t for
wamr, wasmtime, and wasmedge returned a signed integer type. For uint32
values high enough to be in the negative range, sign extension would be
applied when the value was coerced into proxy_wasm::Word. This resulted
in Word values that did not match the comment on Word
```
// Represents a Wasm-native word-sized datum. On 32-bit VMs, the high bits are always zero.
// The Wasm/VM API treats all bits as significant.
```
nor the exact value returned from the wasm plugin.
Signed-off-by: Matt Leon <mattleon@google.com>
0 commit comments