Automatically add subproofs to parallelized execution once they become available #2065
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
tothtamas28
reviewed
Sep 8, 2023
|
|
…ntimeverification/evm-semantics into noah/branches-parallelization
…ntimeverification/evm-semantics into noah/branches-parallelization
PetarMax
added a commit
to runtimeverification/pyk
that referenced
this pull request
Sep 18, 2023
Closes #632. Before introducing a branch, simplify each of the would-be new nodes and see if they simplify to bottom If there are more than 1 non-bottom node, add all these simplified nodes to the CFG, creating a split/branch. If not, simply continue straight-line execution. This should reduce eliminate some infeasible branching by simplifying earlier in the process. Also should eliminate repeated branching encountered in runtimeverification/evm-semantics#2065 when creating new proofs from branches. --------- Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Petar Maksimović <PetarMax@users.noreply.github.com>
…ntimeverification/evm-semantics into noah/branches-parallelization
nwatson22
commented
Sep 19, 2023
…ntimeverification/evm-semantics into noah/branches-parallelization
…ntimeverification/evm-semantics into noah/branches-parallelization
…ntimeverification/evm-semantics into noah/branches-parallelization
Baltoli
pushed a commit
to runtimeverification/k
that referenced
this pull request
Apr 9, 2024
Closes #632. Before introducing a branch, simplify each of the would-be new nodes and see if they simplify to bottom If there are more than 1 non-bottom node, add all these simplified nodes to the CFG, creating a split/branch. If not, simply continue straight-line execution. This should reduce eliminate some infeasible branching by simplifying earlier in the process. Also should eliminate repeated branching encountered in runtimeverification/evm-semantics#2065 when creating new proofs from branches. --------- Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Petar Maksimović <PetarMax@users.noreply.github.com>
Baltoli
pushed a commit
to runtimeverification/k
that referenced
this pull request
Apr 9, 2024
Closes #632. Before introducing a branch, simplify each of the would-be new nodes and see if they simplify to bottom If there are more than 1 non-bottom node, add all these simplified nodes to the CFG, creating a split/branch. If not, simply continue straight-line execution. This should reduce eliminate some infeasible branching by simplifying earlier in the process. Also should eliminate repeated branching encountered in runtimeverification/evm-semantics#2065 when creating new proofs from branches. --------- Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Petar Maksimović <PetarMax@users.noreply.github.com>
Baltoli
pushed a commit
to runtimeverification/k
that referenced
this pull request
Apr 9, 2024
Closes #632. Before introducing a branch, simplify each of the would-be new nodes and see if they simplify to bottom If there are more than 1 non-bottom node, add all these simplified nodes to the CFG, creating a split/branch. If not, simply continue straight-line execution. This should reduce eliminate some infeasible branching by simplifying earlier in the process. Also should eliminate repeated branching encountered in runtimeverification/evm-semantics#2065 when creating new proofs from branches. --------- Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Petar Maksimović <PetarMax@users.noreply.github.com>
Baltoli
pushed a commit
to runtimeverification/k
that referenced
this pull request
Apr 10, 2024
Closes #632. Before introducing a branch, simplify each of the would-be new nodes and see if they simplify to bottom If there are more than 1 non-bottom node, add all these simplified nodes to the CFG, creating a split/branch. If not, simply continue straight-line execution. This should reduce eliminate some infeasible branching by simplifying earlier in the process. Also should eliminate repeated branching encountered in runtimeverification/evm-semantics#2065 when creating new proofs from branches. --------- Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Petar Maksimović <PetarMax@users.noreply.github.com>
Baltoli
pushed a commit
to runtimeverification/k
that referenced
this pull request
Apr 10, 2024
Closes #632. Before introducing a branch, simplify each of the would-be new nodes and see if they simplify to bottom If there are more than 1 non-bottom node, add all these simplified nodes to the CFG, creating a split/branch. If not, simply continue straight-line execution. This should reduce eliminate some infeasible branching by simplifying earlier in the process. Also should eliminate repeated branching encountered in runtimeverification/evm-semantics#2065 when creating new proofs from branches. --------- Co-authored-by: devops <devops@runtimeverification.com> Co-authored-by: Petar Maksimović <PetarMax@users.noreply.github.com>
|
Closing due to age. |
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.