Skip to content

Commit

Permalink
Use unknown as expected verdicts (#611)
Browse files Browse the repository at this point in the history
and adapt comment
  • Loading branch information
schuessf committed Feb 21, 2023
1 parent 67fa941 commit 86f7848
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 9 deletions.
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
// #Safe
// #Unknown
// Reveals bug of issue #441.
// https://github.com/ultimate-pa/ultimate/issues/441
// Computations of pre, sp, wp, and interprocedural sequential composition
Expand Down
Original file line number Diff line number Diff line change
@@ -1,17 +1,12 @@
//#Safe
//#Unknown
// Author: [email protected]
// Date: 2015-08-14
//
// Test for the overapproximation tool directive that we pass to Ultimate via attributes.
//
// Our wiki says the following.
// If a function func has the attribute {:overapproximation "bar"} our model checkers will never output a counterexample that contains func. Instead our model checkers might say unknown and that an overapproximation of bar is the reason for saying unknown.
//
// In fact, this program is not safe (resp. it is only safe with respect to
// the assumption that the semantics of ~bitwiseAnd is a bitwise complement for
// a two's complement representation of the inputs), but we use this file that
// Ultimate does not output the result UNSAFE.

// If a function func has the attribute {:overapproximation "bar"} our model checkers will never output a counterexample that contains func.
// Instead our model checkers might say unknown and that an overapproximation of bar is the reason for saying unknown.

function { :overapproximation "bitwiseAnd" } ~bitwiseAnd(in0 : int, in1 : int) returns (out : int);

Expand Down

0 comments on commit 86f7848

Please sign in to comment.