Coder Social home page Coder Social logo

Comments (5)

keithw avatar keithw commented on July 20, 2024 1

Awesome. In other words, if I encounter any state and data race-related issues with this type of usage, I can assume it's a bug?

Yeah, definitely please let us know.

from wabt.

jonathanmarvens avatar jonathanmarvens commented on July 20, 2024

Upon further investigation, the commentary on #2189 and #2332 seem to imply that the module instances are thread-safe, but the semantics arenโ€™t clear.

To be clear, my current understanding is that the runtime is explicitly thread-safe (if each thread is properly initialized via wasm_rt_init_thread()), but individual module instances might be operating in undefined behavior territory when called into from multiple threads.

from wabt.

keithw avatar keithw commented on July 20, 2024

Normally when we say code is "thread-safe," we're talking about different threads executing code in parallel. Happy to go down that road, but that doesn't seem to be what you're asking about here. If I understand the question, you're just saying, is it okay if a module is instantiated by thread A, and then (after that has provably completed) thread B calls an exported function from that module instance, and then (after that has provably completed) thread C calls an exported function from the same module instance?

Certainly our intention is that this is an easy case and there's no problem. There's no long-lived association between any per-thread state and any particular module instance.

from wabt.

jonathanmarvens avatar jonathanmarvens commented on July 20, 2024

If I understand the question, you're just saying, is it okay if a module is instantiated by thread A, and then (after that has provably completed) thread B calls an exported function from that module instance, and then (after that has provably completed) thread C calls an exported function from the same module instance?

Yes, this is exactly what I'm trying to understand. My apologies if I wasn't clear enough.

Certainly our intention is that this is an easy case and there's no problem. There's no long-lived association between any per-thread state and any particular module instance.

Awesome. In other words, if I encounter any state and data race-related issues with this type of usage, I can assume it's a bug?

from wabt.

jonathanmarvens avatar jonathanmarvens commented on July 20, 2024

Yeah, definitely please let us know.

Will do. Thank you!

(I'll close this issue now, since I got my answer.)

from wabt.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.