PiCoPress requested wasmtime-compiler-reviewers for a review on PR #8192.
PiCoPress requested abrown for a review on PR #8192.
PiCoPress requested wasmtime-core-reviewers for a review on PR #8192.
PiCoPress requested wasmtime-default-reviewers for a review on PR #8192.
PiCoPress requested alexcrichton for a review on PR #8192.
PiCoPress opened PR #8192 from PiCoPress:main
to bytecodealliance:main
:
Planning compiling recusively may takes new vision of WebAssembly, but there are many issues when building.
- Rust seems not to support WASI on stable version fully.
- Unable to decide platform - Unix, Windows - of the WASM runtime. WASM cannot be regarded as OS. According to target naiming, then I assumed corresponding platform is WASI.
- WASM Architecture is hardly different the other existings(x86_64, aarch64, etc.), therefore that just re-using code is no achieves.
github-actions[bot] commented on PR #8192:
Subscribe to Label Action
cc @cfallin, @fitzgen, @peterhuene
<details>
This issue or pull request has been labeled: "cranelift", "cranelift:meta", "isle", "wasmtime:c-api"Thus the following users have been cc'd because of the following labels:
- cfallin: isle
- fitzgen: isle
- peterhuene: wasmtime:c-api
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
bjorn3 submitted PR review.
bjorn3 created PR review comment:
nit: missing trailing newline
bjorn3 submitted PR review.
bjorn3 created PR review comment:
nit: missing trailing newline
bjorn3 submitted PR review.
bjorn3 created PR review comment:
And in all other files.
bjorn3 submitted PR review.
bjorn3 created PR review comment:
Why these empty files? You can omit the
mod wasm32;
, right?
bjorn3 submitted PR review.
bjorn3 created PR review comment:
)]
The isle generated files may contain constructs that trigger these lints as avoiding them would make the emitting code more complex without much benefit.
Is your intent here to make a wasmtime compiled for wasi able to cross-compile to other architectures without running anything? Or to run code that uses wasmtime on wasi? In the latter case there will need to be a new interface to allow jitted code to actually run, at which point it can probably pass the wasm module given by the user of the wasmtime api could likely directly be passed to the host wasm engine without any translation by wasmtime.
PiCoPress commented on PR #8192:
Wasmtime built by wasm32(I will call as Meta-WASM) could simplify development processes between implementing real hardware architecture and wasmtime architecture. However I recently found the problem that it makes irony, although Meta-WASM needs the Wasmtime, also Wasmtime may needs the Meta-WASM to execute completely.
And there are some other techincal issues with JIT.Are you agree to proceed this PR?
PiCoPress updated PR #8192.
PiCoPress closed without merge PR #8192.
Last updated: Dec 23 2024 at 12:05 UTC