Skip to content

Distinguish \bottom from stuck states #2451

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

Merged
merged 13 commits into from
Mar 16, 2021

Conversation

andreiburdusa
Copy link
Contributor

@andreiburdusa andreiburdusa commented Mar 10, 2021

When the last configuration rewrites to \bottom, the backend will report that instead of reporting the last configuration as "stuck".

Fixes #2445.


Review checklist

The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

  • Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
  • Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
  • Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
  • Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

@ttuegel ttuegel self-requested a review March 15, 2021 16:10
Copy link
Contributor

@ttuegel ttuegel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wrote a summary in the pull request description, but please do that in the future.

configs <- lift $ Pattern.simplifyTopConfiguration config
filteredConfigs <- SMT.Evaluator.filterMultiOr configs
asum (pure <$> toList filteredConfigs)
if filteredConfigs == mempty
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if filteredConfigs == mempty
if null filteredConfigs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, disregard this comment. I added it before you changed this line, but for some reason the review didn't go through.

@rv-jenkins rv-jenkins merged commit 0427fae into master Mar 16, 2021
@rv-jenkins rv-jenkins deleted the distinguish-bottom-from-stuck-states branch March 16, 2021 14:49
goodlyrottenapple added a commit that referenced this pull request Aug 9, 2023
Another attempt at addressing
runtimeverification/evm-semantics#1944.
Addresses #3630 (needs a follow-up in booster)

This change mimicks what kore-exe in prover mode returns(as introduced
by #2451),
namely the configuration goes to bottom
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

krun should distinguish \bottom from stuck states
4 participants