meheff
meheff
For the purpose of referring to things, it might be good to give spawn statements names: ``` baz: spawn foo; ``` This gives you a string path for referring to...
@mczyz-antmicro You're correct that proc-scoped channels will solve the issues you describe. Regarding implementing this as metadata, that could be done but I don't think it is the most robust...
The IR has supported proc-scoped channels for a while. Optimizations and codegen also generally support the feature though there may be some corner cases or missing features. The big missing...
I presume fatal is expected to terminate the simulation/evaluation? The fatal/error/info levels also matches the Google C++ logging library levels (and others I presume). Numeric verbosity levels in trace statements...
I agree with @ericastor that matching interpreter and hardware behavior generally for latency sensitive operations is really hard to do if not impossible and shouldn't stop us from implementing a...
I think this would not be too hard to implement. Most of the work would probably be in codegen. @hongted Regarding changes to the evaluation infrastructure (jit/interpreter): are these changes...
I agree with @mikex-oss and @ericastor that the name is a bit confusing and `try_send` or whatever would be more precise. I suppose we should rename the corresponding receive operation...
@cdleary FYI
I just rebased this. Let me know if you need anything else.
Any progress on this? Thanks.