Stream: wasmtime

Topic: move GlobalFrameInfo into wasmtime-runtime?


view this post on Zulip fitzgen (he/him) (May 27 2020 at 18:31):

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

view this post on Zulip Alex Crichton (May 27 2020 at 18:35):

hm so in general I think we have basically 1 global at most for everything

view this post on Zulip Alex Crichton (May 27 2020 at 18:35):

so I'd prefer to avoid having two, one in the api and one in runtime

view this post on Zulip Alex Crichton (May 27 2020 at 18:36):

moving it around seems fine though

view this post on Zulip Alex Crichton (May 27 2020 at 18:36):

ideally though it'd be no global but an explicitly passed in context

view this post on Zulip Alex Crichton (May 27 2020 at 18:36):

the global part is only b/c of Trap::new right now

view this post on Zulip Alex Crichton (May 27 2020 at 18:36):

which takes no contextual argument


Last updated: Nov 22 2024 at 16:03 UTC