top | item 45281522 (no title) TrueDuality | 5 months ago The irony for me is that it's already slow because of the lack of native 64-bit math. I don't care about the memory space available nearly as much. discuss order hn newest sehugg|5 months ago Eh? I'm pretty sure it's had 64-bit math for awhile -- i64.add, etc. jesse__|5 months ago They might have meant lack of true 64bit pointers ..? IIRC the chrome wasm runtime used tagged pointers. That comes with an access cost of having to mask off the top bits. I always assumed that was the reason for the 32bit specification in v1 unknown|5 months ago [deleted]
sehugg|5 months ago Eh? I'm pretty sure it's had 64-bit math for awhile -- i64.add, etc. jesse__|5 months ago They might have meant lack of true 64bit pointers ..? IIRC the chrome wasm runtime used tagged pointers. That comes with an access cost of having to mask off the top bits. I always assumed that was the reason for the 32bit specification in v1 unknown|5 months ago [deleted]
jesse__|5 months ago They might have meant lack of true 64bit pointers ..? IIRC the chrome wasm runtime used tagged pointers. That comes with an access cost of having to mask off the top bits. I always assumed that was the reason for the 32bit specification in v1
sehugg|5 months ago
jesse__|5 months ago
unknown|5 months ago
[deleted]