Updates from master #916
Merged
Updates from master #916
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: devops <devops@runtimeverification.com>
From commit 8db489b. Co-authored-by: Daniel Cumming <124537596+dkcumming@users.noreply.github.com>
Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Daniel Cumming <124537596+dkcumming@users.noreply.github.com>
…#907) Add CLI options for semantics summarization evaluation: 1. `--to-module <file>` for `kmir show`: - Export proof KCFG as K module to specified file - Supports .json (KFlatModule JSON format) and .k (K text format) 2. `--minimize-proof` for `kmir show`: - Minimize the proof KCFG before displaying or exporting - Saves minimized proof back to disk 3. `--add-module <file>` for `kmir prove-rs`: - Load K module files and inject their rules into the definition - Can be specified multiple times for multiple modules - Currently supports JSON format only These features enable the workflow: kmir prove-rs -> kmir show --to-module --minimize-proof -> kmir prove-rs --add-module
This enables the extension of the `KMIR` K module with abstractions, cheatcodes and the like without having to duplicate the whole `kmir` machinery.
…T>` (#913) When iterating through a collection, the elements of the the range of the collection are transmuted from `T` to `std::mem::MaybeUninit<T>`. Previously this thunked (as can be seen in the `run-smir-random` tests), but the new rules allow for element-wise transmutation _specifically_ for the case seen in iterators. Not added in this PR is the ability to read from these which is a more complicated process of interpretting a `PtrToPtr` conversion on a transparent wrapper types which do not currently support non-zero union field access. This is a problem for this as field `1` of `MaybeUninit` corresponds to the case that is initialised. See #914
Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Tamás Tóth <tothtamas28@users.noreply.github.com>
Collaborator
|
The merge conflict I think is due the the changes @tothtamas28 made and I approved for the smj update. I will try to fix locally now! |
dkcumming
approved these changes
Jan 21, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MaybeUninitcases (element updates within arrays)