I need access to GlobalFrameInfo
(for stack maps) in a libcall, and libcalls are defined in wasmtime-runtime, but GlobalFrameInfo
is in the wasmtime-api
crate.
Is it reasonable to move GlobalFrameInfo
into wasmtime-runtime
? Or should I make something akin to GlobalFrameInfo
but which only contains stack maps and lives inside wasmtime-runtime
?
cc @Alex Crichton
hm so in general I think we have basically 1 global at most for everything
so I'd prefer to avoid having two, one in the api and one in runtime
moving it around seems fine though
ideally though it'd be no global but an explicitly passed in context
the global part is only b/c of Trap::new
right now
which takes no contextual argument
Last updated: Dec 23 2024 at 13:07 UTC