Wasmtime GitHub notifications bot (May 01 2020 at 15:47): Wasmtime GitHub notifications bot (May 01 2020 at 15:47):alexcrichton labeled Issue #1642:
This I believe is a current hole in the MachInst backend for ARM64 right now which is causing a number of wasmtime tests to fail. At least for aarch64-unknown-linux-gnu we'll need to emit DWARF unwind information from the backend similar to how we do so for x86_64-unknown-linux-gnu. Since this isn't implemented today tests related to traps fail because we can't backtrace through wasm and get all the native frames which correspond to wasm frames.
I'm filing this to use as a tracking issue and attach to some FIXME statements!
Wasmtime GitHub notifications bot (May 01 2020 at 15:47):alexcrichton opened Issue #1642:
This I believe is a current hole in the MachInst backend for ARM64 right now which is causing a number of wasmtime tests to fail. At least for aarch64-unknown-linux-gnu we'll need to emit DWARF unwind information from the backend similar to how we do so for x86_64-unknown-linux-gnu. Since this isn't implemented today tests related to traps fail because we can't backtrace through wasm and get all the native frames which correspond to wasm frames.
I'm filing this to use as a tracking issue and attach to some FIXME statements!
Wasmtime GitHub notifications bot (Jun 29 2020 at 15:55):bnjbvr labeled Issue #1642:
This I believe is a current hole in the MachInst backend for ARM64 right now which is causing a number of wasmtime tests to fail. At least for aarch64-unknown-linux-gnu we'll need to emit DWARF unwind information from the backend similar to how we do so for x86_64-unknown-linux-gnu. Since this isn't implemented today tests related to traps fail because we can't backtrace through wasm and get all the native frames which correspond to wasm frames.
I'm filing this to use as a tracking issue and attach to some FIXME statements!
Wasmtime GitHub notifications bot (Jun 29 2020 at 15:55):github-actions[bot] commented on Issue #1642:
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 (Nov 06 2020 at 15:13):yurydelendik commented on Issue #1642:
As defined, this issue addressed and fixed by #2313.
Wasmtime GitHub notifications bot (Nov 06 2020 at 15:13):yurydelendik closed Issue #1642:
This I believe is a current hole in the MachInst backend for ARM64 right now which is causing a number of wasmtime tests to fail. At least for aarch64-unknown-linux-gnu we'll need to emit DWARF unwind information from the backend similar to how we do so for x86_64-unknown-linux-gnu. Since this isn't implemented today tests related to traps fail because we can't backtrace through wasm and get all the native frames which correspond to wasm frames.
I'm filing this to use as a tracking issue and attach to some FIXME statements!
Last updated: Nov 22 2024 at 16:03 UTC