-
Notifications
You must be signed in to change notification settings - Fork 109
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
Tracking issue for MIR linker #1588
Milestone
Comments
This was referenced Aug 26, 2022
4 tasks
4 tasks
celinval
added a commit
that referenced
this issue
Sep 20, 2022
Add a new module reachability which implements the reachability algorithm. Add the end to end logic for the reachability starting from all the harnesses in the target crate. ## Resolved issues: Resolves #1672 ## Related RFC: #1588 ## Call-outs: We still need to build the custom sysroot in order to fix the missing functions issue. I added a mechanism to run the regression tests using the MIR linker inside compiletest. I ran the regression manually (with the mir_linker enabled) the only tests that didn't pass were: cargo-kani/asm/global_error/doesnt_call_crate_with_global_asm.expected: The global assembly is out of the scope so it doesn't get processed. If we want to keep that behavior, we will have to inspect all items manually. cargo-kani/cargo-tests-dir/expected: This might be a legit issue that I need to fix on kani-driver logic. cargo-ui/dry-run/expected: Not an issue (arguments to the compiler changes).
4 tasks
This was referenced Oct 4, 2022
Merged
This was referenced Oct 14, 2022
This was referenced Oct 24, 2022
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
This is a tracking issue for the RFC
mir_linker
which will enable users to use non-generic + non-inlined methods of the standard library.During development, this feature will be gated by the unstable option
--mir-linker
.Major Steps
Suggestion of major steps:
--reachability=[legacy | none | harnesses]
--mir-linker
.--reachability=pub_fns
.Open Questions
kani setup
?The text was updated successfully, but these errors were encountered: