Closed Ketchynez closed 2 years ago
@Ketchynez how did you configure boolector
? Can you provide any more information on this?
I just ran this with the latest master
and with --only-cadical
(passed to ./configure.sh
):
[avj@tempvm build]$ ./bin/boolector --version
3.2.1
[avj@tempvm build]$ ./bin/boolector --copyright
This software is
Copyright (c) 2007-2009 Robert Brummayer
Copyright (c) 2007-2018 Armin Biere
Copyright (c) 2012-2019 Aina Niemetz, Mathias Preiner
This software is linked against CaDiCaL
Copyright (c) 2016-2019 Armin Biere
[avj@tempvm build]$ /usr/bin/time -vvv ./bin/boolector -m ../test.smt2
sat
((P1_PHASE #b0001110111))
(model
(define-fun P1_PHASE () (_ BitVec 10) #b0001110111)
)
(model
(define-fun P1_PHASE () (_ BitVec 10) #b0001110111)
)
Command exited with non-zero status 10
Command being timed: "./bin/boolector -m ../test.smt2"
User time (seconds): 0.00
System time (seconds): 0.00
Percent of CPU this job got: 50%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 3552
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 322
Voluntary context switches: 1
Involuntary context switches: 0
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 10
Okay, so with all the solvers enabled:
[avj@tempvm build]$ for i in cadical cms lingeling minisat picosat; do echo $i; /usr/bin/time -vvv ./bin/boolector -SE $i -m ../test.smt2 |& grep "wall"; done
cadical
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
cms
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
lingeling
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.26
minisat
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.01
picosat
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
So I guess you're doing it with Lingeling?
Hi!
Found a constraint, which is rather simple, but the operating time is noticeably longer than on cvc4 and z3 (unlike other bitvector scenarious where boolector was always faster), looks kinda weird. Timings: Z3: 0.038 sec CVC4: 0.020 sec Boolector: 0.360 sec
Here is the constraint