Skip to content
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

Equivalence checking: split 'erroneous' into 'unequivalent' and 'unsafe' #1435

Merged
merged 1 commit into from
Sep 4, 2023

Conversation

mario-bucev
Copy link
Collaborator

We now distinguish between a candidate function being incorrect due to unsafety (e.g. division by zero) or due to not being equivalent. Previously, these two kinds of incorrectness were merged into one category.

@vkuncak vkuncak merged commit de7a2a8 into epfl-lara:main Sep 4, 2023
2 checks passed
@mario-bucev mario-bucev deleted the equivchk-unsafe-split branch September 5, 2023 08:19
@@ -301,7 +308,7 @@ class EquivalenceCheckingRun private(override val component: EquivalenceChecking
val lStr = l.map(_.fullName)
info(s"List of functions that are equivalent to model ${m.fullName}: ${lStr.mkString(", ")}")
}
val errns = res.erroneous.keys.toSeq.map(_.fullName).sorted.mkString(", ")
val errns = res.unequivalent.keys.toSeq.map(_.fullName).sorted.mkString(", ")
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we also print the list of unsafe functions here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants