Ben L. Titzer
Ben L. Titzer
Another possibility is to use a module that has an imported memory and put the function in that module. Thus the function is parameterized over memory by virtue of the...
Not for memory 0; the interpreter caches its base in a register and uses the same virtual memory protections for OOB access as JIT-compiled code does.
Oh, indeed, could be a nice idea. I'll think on that a bit.
This does mean an additional subtract (of `1`) in the interpreter, while JIT code will be specialized to the 64-bittitude of the memory and the offset immediate, allowing the `-1`...
Let's chat about it in the meeting.
We decided not to require a flag bit.
Languages that have well-defined behavior on e.g., division by zero or access of a null pointer (in the GC proposal), will want to catch traps and generate source-level exceptions. Otherwise,...
IIUC @justinmichaud is proposing that pointers be *semantically* 34-bits (or as declared) and the engine is required to *ignore* the upper bits of the index.
It's worth noting that `x86-64` still has the `FS` and `GS` segments, but they are only a base; the limit is ignored by all current CPUs. The other segment registers...
Can we add a logistical note to the page to put the Google office address (for those scheduling hotels)? Thanks.