-
Notifications
You must be signed in to change notification settings - Fork 1.8k
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#14003 In bytecodealliance/wasmtime;
Dead-store-elimination changing behavior of fuzz-generated program
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingcraneliftIssues related to the Cranelift code generatorIssues related to the Cranelift code generatorStatus: Open.#13990 In bytecodealliance/wasmtime;Winch fails to compile atomic.rmw.or on x86_64
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingwasm-proposal:threadsIssues related to the WebAssembly threads proposalIssues related to the WebAssembly threads proposalwinchWinch issues or pull requestsWinch issues or pull requestsStatus: Open.#13989 In bytecodealliance/wasmtime;Memory.atomic.wait instructions fail to account for big-endian hosts
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingwasm-proposal:threadsIssues related to the WebAssembly threads proposalIssues related to the WebAssembly threads proposalStatus: Open.#13988 In bytecodealliance/wasmtime;Component-model fixed-length-lists aren't integrated with WAVE printing
wasm-proposal:component-modelIssues related to the WebAssembly Component Model proposalIssues related to the WebAssembly Component Model proposalStatus: Open.#13984 In bytecodealliance/wasmtime;Core dumps don't handle composed adapters in components
wasmtime:debuggingIssues related to debugging of JIT'ed codeIssues related to debugging of JIT'ed codeStatus: Open.#13983 In bytecodealliance/wasmtime;MPK does not reset protection keys after fresh mmaps
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingwasmtime:pooling-allocatorIssues related to Wasmtime's pooling allocatorIssues related to Wasmtime's pooling allocatorStatus: Open.#13982 In bytecodealliance/wasmtime;Unchecked memory consumption with
memory.atomic.wait{32,64}wasm-proposal:threadsIssues related to the WebAssembly threads proposalIssues related to the WebAssembly threads proposalStatus: Open.#13981 In bytecodealliance/wasmtime;Fixed-length lists can overflow in ABI calculations for the size of the list
wasm-proposal:component-modelIssues related to the WebAssembly Component Model proposalIssues related to the WebAssembly Component Model proposalStatus: Open.#13980 In bytecodealliance/wasmtime;FACT can't handle async-to-async adapters using memory64
wasm-proposal:component-modelIssues related to the WebAssembly Component Model proposalIssues related to the WebAssembly Component Model proposalwasm-proposal:memory64Issues with the implementation of the memory64 wasm proposalIssues with the implementation of the memory64 wasm proposalStatus: Open.#13979 In bytecodealliance/wasmtime;aarch64: Cranelift's apple_aarch64 calling convention writes past the end of outgoing arguments
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingcraneliftIssues related to the Cranelift code generatorIssues related to the Cranelift code generatorcranelift:area:aarch64Issues related to AArch64 backend.Issues related to AArch64 backend.Status: Open.#13973 In bytecodealliance/wasmtime;aarch64: Atomic umin/umax does not zero-extend properly
bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixingcraneliftIssues related to the Cranelift code generatorIssues related to the Cranelift code generatorcranelift:area:aarch64Issues related to AArch64 backend.Issues related to AArch64 backend.Status: Open.#13972 In bytecodealliance/wasmtime;