Skip to content
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

Rules for substrBytes #1264

Closed

Conversation

hjorthjort
Copy link
Contributor

It was suggested these rules from the Ewasm semantics should be upstreamed.

@hjorthjort hjorthjort changed the title Bytes symbolic lemmas Rules for substrBytes May 6, 2020
@dwightguth
Copy link
Collaborator

If these are intended for use for the haskell backend, they should not be in a module marked [kast].

@ehildenb
Copy link
Member

ehildenb commented May 8, 2020

They should specifically be in a module marked kore (llvm and haskell backends), or symbolic, kore (haskell backend). kast is for ocaml/java backend.

@hjorthjort
Copy link
Contributor Author

It should be for the Haskell backend. Looking here, I assume the module should be named BYTES-KORE-SYMBOLIC. https://github.com/kframework/k/blob/e45e3d9359f428680a4c07c494cb831fc8636ef4/k-distribution/include/builtin/domains.k#L161

@hjorthjort
Copy link
Contributor Author

Not sure about what the right import is: BYTES-IN-K or BYTES-KORE. The lemmas are based on the semantics described in BYTES-IN-K.

@dwightguth
Copy link
Collaborator

It should probably import BYTES-KORE because that's what the haskell backend uses.

@ehildenb
Copy link
Member

@hjorthjort please update this to (i) remove all the #Ceil rules, and (ii) port to the markdown format files.

@ehildenb
Copy link
Member

Closing as this is likely outdated and has horrible conflicts at this point. Re-open if still needed @hjorthjort .

@ehildenb ehildenb closed this Apr 13, 2021
@hjorthjort hjorthjort deleted the bytes-symbolic-lemmas branch April 14, 2021 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants