Skip to content
This repository was archived by the owner on Apr 25, 2024. It is now read-only.

Automating implication-every-block reasoning #580

Merged
merged 3 commits into from
Aug 7, 2023

Conversation

PetarMax
Copy link
Contributor

@PetarMax PetarMax commented Aug 7, 2023

This PR removes the need for the implication-every-block parameter in APR-related provers. The reasoning is as follows:

  • if the target node is a terminal node, then subsumption into target should be checked only for terminal nodes (equivalent to previously setting implication-every-block to false)
  • otherwise (and this is possible, for example, for internal functions), subsumption into target is checked on every block ((equivalent to previously setting implication-every-block to true).

I am assuming that this change requires changes to KEVM so that the implication-every-block parameter is removed.

@PetarMax PetarMax requested review from geo2a and ehildenb August 7, 2023 10:17
@PetarMax PetarMax merged commit f1a22bb into master Aug 7, 2023
@PetarMax PetarMax deleted the auto-implication-every-block branch August 7, 2023 15:01
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 9, 2024
…yk#580)

This PR removes the need for the `implication-every-block` parameter in
APR-related provers. The reasoning is as follows:
- if the `target` node is a `terminal` node, then subsumption into
target should be checked only for `terminal` nodes (equivalent to
previously setting `implication-every-block` to `false`)
- otherwise (and this is possible, for example, for internal functions),
subsumption into target is checked on every block ((equivalent to
previously setting `implication-every-block` to `true`).

I am assuming that this change requires changes to KEVM so that the
`implication-every-block` parameter is removed.

---------

Co-authored-by: devops <[email protected]>
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 9, 2024
…yk#580)

This PR removes the need for the `implication-every-block` parameter in
APR-related provers. The reasoning is as follows:
- if the `target` node is a `terminal` node, then subsumption into
target should be checked only for `terminal` nodes (equivalent to
previously setting `implication-every-block` to `false`)
- otherwise (and this is possible, for example, for internal functions),
subsumption into target is checked on every block ((equivalent to
previously setting `implication-every-block` to `true`).

I am assuming that this change requires changes to KEVM so that the
`implication-every-block` parameter is removed.

---------

Co-authored-by: devops <[email protected]>
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 10, 2024
…yk#580)

This PR removes the need for the `implication-every-block` parameter in
APR-related provers. The reasoning is as follows:
- if the `target` node is a `terminal` node, then subsumption into
target should be checked only for `terminal` nodes (equivalent to
previously setting `implication-every-block` to `false`)
- otherwise (and this is possible, for example, for internal functions),
subsumption into target is checked on every block ((equivalent to
previously setting `implication-every-block` to `true`).

I am assuming that this change requires changes to KEVM so that the
`implication-every-block` parameter is removed.

---------

Co-authored-by: devops <[email protected]>
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 10, 2024
…yk#580)

This PR removes the need for the `implication-every-block` parameter in
APR-related provers. The reasoning is as follows:
- if the `target` node is a `terminal` node, then subsumption into
target should be checked only for `terminal` nodes (equivalent to
previously setting `implication-every-block` to `false`)
- otherwise (and this is possible, for example, for internal functions),
subsumption into target is checked on every block ((equivalent to
previously setting `implication-every-block` to `true`).

I am assuming that this change requires changes to KEVM so that the
`implication-every-block` parameter is removed.

---------

Co-authored-by: devops <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants