-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
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
call
causes state splitting
#273
Comments
To reproduceThis was discovered on commit 96f3642e6e3917d38bf827aa5a8f80dc97030542 on the ewasm-semantics repository From directory |
What does the associated K rule look like? |
|
Hmmmm, I wonder if it's splitting on the Though it's also a nested |
That's probably what is going on. Although the lookups in question are using I'm wondering if it will help adding a Another thing that might be tripping up the backend is that the rules for |
Well, I think what's more likely is that the backend is not fully evaluating
|
A more general solution to this would be to find a way to eliminate |
I'll try that. Yes, ideally |
The below screenshot of the execution graph in the Haskell backend shows the splitting at axiom 112, which is
call
. The splitting occurs in node 94 and 111.This is when calling the
"main"
function ofwrc20
after the module has been loaded.Axiom 112
The text was updated successfully, but these errors were encountered: