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

kmir execution should be enabled for any functions #165

Open
yanliu18 opened this issue Jun 28, 2023 · 0 comments
Open

kmir execution should be enabled for any functions #165

yanliu18 opened this issue Jun 28, 2023 · 0 comments
Labels
mir-semantics MIR semantics in K

Comments

@yanliu18
Copy link
Contributor

rule <k> #initialized() => #executeFunctionLike(Fn(String2IdentifierToken("main"):: .FunctionPath), .ArgumentList) ... </k>

The above implementation ensures a MIR file always starts with the main function, which is consistent with the rust code execution rules.

However, we should allow MIR file to analyse any functions, for example, kmir should be able to execute the add function.

In this way, we treat functions as the main unit for analysis rather than the rust code file, enabling more flexibility.

@yanliu18 yanliu18 added the mir-semantics MIR semantics in K label Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mir-semantics MIR semantics in K
Projects
None yet
Development

No branches or pull requests

1 participant