From 52bab1414d41a4beb301f3c8a4165fa972f71a93 Mon Sep 17 00:00:00 2001 From: Gereon Kremer Date: Mon, 31 Aug 2020 21:59:39 +0200 Subject: Fix --ackermann in the presence on syntactically different but possibly equal selects (#4981) The implementation of --ackermann mishandled selects in a subtle way: If select is applied to two syntactically different arrays (that may be semantically equal), the ackermann preprocessing failed to generate the "all arguments equal implies terms equal" lemmas. The problem is that we used the first argument (that is: the array) as lookup to identify terms that need to be considered for these lemmas. Instead we now use their operator (select) just like for uninterpreted function applications. Fixes #4957 . Also adds a regression. --- test/regress/regress0/arrays/bug4957.smt2 | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 test/regress/regress0/arrays/bug4957.smt2 (limited to 'test/regress/regress0/arrays/bug4957.smt2') diff --git a/test/regress/regress0/arrays/bug4957.smt2 b/test/regress/regress0/arrays/bug4957.smt2 new file mode 100644 index 000000000..f82ae1932 --- /dev/null +++ b/test/regress/regress0/arrays/bug4957.smt2 @@ -0,0 +1,6 @@ +; COMMAND-LINE: --ackermann --no-check-unsat-cores +; EXPECT: unsat +(set-logic QF_ALIA) +(declare-fun a () (Array Int Int)) +(assert (distinct (select a 0) (select (ite false a a) 0))) +(check-sat) -- cgit v1.2.3