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
WebAssembly does not guarantee constant time integer operations
It may be the case that certain 64-bit platforms that currently use the 32-bit code path will perform better with the 64-bit code path, despite the lack of compiler optimization for the relevant math/bits intrinsics. As I do not have access to the various targets, benchmark results showing this will be welcome.
WASM is supported now due to the growing popularity of the target, however WebAssembly3 does not mandate nor guarantee instruction timings. The standard techniques used to mitigate timing side-channels work under the assumption that certain things are constant-time with regards to the inputs, which may not be true.
The text was updated successfully, but these errors were encountered:
This serves as a tracking issue to document which targets1 are supported, along with ancillary information.
bits.Add64
/bits.Mul64
are slowbits.Add64
/bits.Mul64
are slowbits.Add64
is slow in released versions2bits.Add64
/bits.Mul64
are slowIt may be the case that certain 64-bit platforms that currently use the 32-bit code path will perform better with the 64-bit code path, despite the lack of compiler optimization for the relevant
math/bits
intrinsics. As I do not have access to the various targets, benchmark results showing this will be welcome.WASM is supported now due to the growing popularity of the target, however WebAssembly3 does not mandate nor guarantee instruction timings. The standard techniques used to mitigate timing side-channels work under the assumption that certain things are constant-time with regards to the inputs, which may not be true.
The text was updated successfully, but these errors were encountered: