Wasmtime GitHub notifications bot (May 04 2020 at 18:04): Wasmtime GitHub notifications bot (May 04 2020 at 18:04):teapotd opened Issue #1651:
In Microsoft x64 calling convention arguments larger than pointer width are passed by reference:
Any argument that doesn't fit in 8 bytes, or isn't 1, 2, 4, or 8 bytes, must be passed by reference. A single argument is never spread across multiple registers. [...] 16-byte arguments are passed by reference.
This means caller should allocate argument on stack and pass pointer to it instead of value in appropriate register/stack slot. Cranelift currently incorrently does the same thing as System V - splits values or pass them in vector registers. See also https://github.com/bytecodealliance/wasmtime/pull/1510#issuecomment-614770451.
[1] https://docs.microsoft.com/en-us/cpp/build/x64-calling-convention
Wasmtime GitHub notifications bot (May 04 2020 at 18:04):teapotd labeled Issue #1651:
In Microsoft x64 calling convention arguments larger than pointer width are passed by reference:
Any argument that doesn't fit in 8 bytes, or isn't 1, 2, 4, or 8 bytes, must be passed by reference. A single argument is never spread across multiple registers. [...] 16-byte arguments are passed by reference.
This means caller should allocate argument on stack and pass pointer to it instead of value in appropriate register/stack slot. Cranelift currently incorrently does the same thing as System V - splits values or pass them in vector registers. See also https://github.com/bytecodealliance/wasmtime/pull/1510#issuecomment-614770451.
[1] https://docs.microsoft.com/en-us/cpp/build/x64-calling-convention
Wasmtime GitHub notifications bot (May 04 2020 at 18:04):teapotd labeled Issue #1651:
In Microsoft x64 calling convention arguments larger than pointer width are passed by reference:
Any argument that doesn't fit in 8 bytes, or isn't 1, 2, 4, or 8 bytes, must be passed by reference. A single argument is never spread across multiple registers. [...] 16-byte arguments are passed by reference.
This means caller should allocate argument on stack and pass pointer to it instead of value in appropriate register/stack slot. Cranelift currently incorrently does the same thing as System V - splits values or pass them in vector registers. See also https://github.com/bytecodealliance/wasmtime/pull/1510#issuecomment-614770451.
[1] https://docs.microsoft.com/en-us/cpp/build/x64-calling-convention
Wasmtime GitHub notifications bot (May 04 2020 at 18:04):github-actions[bot] commented on Issue #1651:
Subscribe to Label Action
cc @bnjbvr
<details>
This issue or pull request has been labeled: "cranelift"Thus the following users have been cc'd because of the following labels:
- bnjbvr: cranelift
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Jun 01 2020 at 18:13):fitzgen closed Issue #1651:
In Microsoft x64 calling convention arguments larger than pointer width are passed by reference:
Any argument that doesn't fit in 8 bytes, or isn't 1, 2, 4, or 8 bytes, must be passed by reference. A single argument is never spread across multiple registers. [...] 16-byte arguments are passed by reference.
This means caller should allocate argument on stack and pass pointer to it instead of value in appropriate register/stack slot. Cranelift currently incorrently does the same thing as System V - splits values or pass them in vector registers. See also https://github.com/bytecodealliance/wasmtime/pull/1510#issuecomment-614770451.
[1] https://docs.microsoft.com/en-us/cpp/build/x64-calling-convention
Last updated: Nov 22 2024 at 16:03 UTC