We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The mutual exclusion pass can create cycles when merging channel operations.
To Reproduce
proc A { cin0: chan<u32> in; cin1: chan<u32> in; config(cin0: chan<u32> in, cin1: chan<u32> in) { (cin0, cin1) } init { false } next(s: bool) { let (tok0, data) = recv_if(join(), cin0, !s, u32:0); let (tok_cin1, _) = recv_if(join(), cin1, !s, u32:0); let (tok1, _) = recv_if(tok_cin1, cin0, s, u32:0); let (tok_cin1, _) = recv_if(tok0, cin1, s, u32:0); data == u32:0 } }
This gives Cycle detected: [tuple_index.87 -> receive.86 -> after_all.83 -> tok0 -> tuple.102 -> tuple_index.98 -> receive.97 -> after_all.94 -> tuple_index.87];
Cycle detected: [tuple_index.87 -> receive.86 -> after_all.83 -> tok0 -> tuple.102 -> tuple_index.98 -> receive.97 -> after_all.94 -> tuple_index.87];
Expected behavior It should either fail to merge one of the receive pairs, or it should correctly merge them without adding a cycle.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
The mutual exclusion pass can create cycles when merging channel operations.
To Reproduce
This gives
Cycle detected: [tuple_index.87 -> receive.86 -> after_all.83 -> tok0 -> tuple.102 -> tuple_index.98 -> receive.97 -> after_all.94 -> tuple_index.87];
Expected behavior
It should either fail to merge one of the receive pairs, or it should correctly merge them without adding a cycle.
The text was updated successfully, but these errors were encountered: