update from upstream #1
Open
+444,590
−149,628
Conversation
This file contains 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
…perly (#4535) Fix: Pi-Squared-Inc/pi2#1644 Unfortunately, Napoleon extensions can't escape `:` and treat everything before it as a type thus, the rendering of this example was outputting a wrong and malformed description of the function as shown below:  As this isn't a key feature description, we chose to remove it to get cleaner documentation:  This is a known issue discussed here: sphinx-doc/sphinx#9273
Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Bruce Collie <brucecollie82@gmail.com>
The upgrade mechanism for HS backend in `k` was broken by some changes to the nix flake which modified the syntax for the `haskell-backend` dependency in `flake.nix`. This PR fixes the update script and updates HS backend to the latest version. * [update-deps.yml] adjusts the `sed` expression * (by manually running the shell script from the above:) - update HS backend to version 0.1.46 - update `flake.lock` to reflect this update
Co-authored-by: devops <devops@runtimeverification.com>
This crash was found by @lucasmt. When there is a structural match failure in failure info computation we were assuming the cells in the antecedent were always present in the consequent, but this is not necessarily true in the case where we have optional cells, e.g. `type="Map"`. This avoids the crash by simply indicating the missing cell is missing from the consequent. There is still confusing behavior when, e.g. there are multiple copies of the same cell.
…for booster (#4533) The previous change #4522 was insufficient to make the equations usable in `booster`. Matches with literal `Int` constants will still be indeterminate, so this PR removes the literals from the rule LHSs. * Use `0 ==Int I` instead of a syntactic _match_ in the equation for argument `0`. This enables evaluating terms with `I ==Int 0` in the path condition. * Remove equation with literal `-1` and widen requires in equation for negative arguments (previously `I <Int -1`, now `I <Int 0`). The result is the same as before with no extra equation required.
Co-authored-by: devops <devops@runtimeverification.com>
Add an `install-build-deps` script to replace the manual commands in the README. See commit message(s) for details. __WARNING:__ This commit is based on the commit in #4054; if you merge this it will merge that one too. (The script includes the `libunwind-dev` package added in that commit.) You'll probably want to do a quick check that this works on MacOS and update the commit message appropriately.
Co-authored-by: devops <devops@runtimeverification.com>
Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Theodoros Kasampalis <kasampalis.theodoros@gmail.com>
This PR adds support for the `L [ I <- X ]` syntax on the LHS of rules, which allows you to pattern match on an arbitrary element of a list. The code is not fully polished; it is not integrated with configuration abstraction or cell collections. It is not likely to be further improved upon presently because the code it was intended to support ended up not proving worth merging. However, it is broadly useful functionality (along with the accompanying LLVM backend PR) and thus ought to be merged. --------- Co-authored-by: Dwight Guth <dwight.guth@runtimeverification.com>
@ACassimiro discovered a bug where we aren't allowing arguments on the `seqstrict` attribute in pyk. This PR addresses this, and enables a previously failing test in `regression-new` that was due to this bug.
This PR disables the trimming of split constraints when showing a KCFG. The reason for this is as follows: - the constraints guide the debugging of Kontrol proofs in many cases, and it is likely that they will serve a similar purpose for other semantics; - if `--no-minimize` is turned on, which disables the trimming, the KCFG will also contain all of the substitutions printed explicitly, which are very large and hinder navigation through the KCFG considerably.
Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Roberto Rosmaninho <robertogomes@dcc.ufmg.br>
1. kcfg.minimize.KCFGMinimizer.merge_node; 2. kcfg.minimize.KCFGMinimizer.minimize; 3. some untils for `merge_node`. --------- Co-authored-by: Everett Hildenbrandt <everett.hildenbrandt@gmail.com>
Co-authored-by: devops <devops@runtimeverification.com>
… module (#4643) This PR exposes a new LLVM Proof Hint event by creating its own Pyk representation class, which the Pi2 MPG Team can use to parse the new Hints version! - This PR depends on the LLVM Backend PR: runtimeverification/llvm-backend#1148 - The K update LLVM Backend PR: #4639 --------- Co-authored-by: rv-jenkins <admin@runtimeverification.com>
This PR adds a recogniser function for loops to the KCFG semantics. This allows us to avoid unnecessary KCFG traversal computation in the cases when the node examined is not a loop head. This computation turned out to be quite expensive in real-world proofs with a high branching factor.
Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Theodoros Kasampalis <kasampalis.theodoros@gmail.com>
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.
No description provided.