Extending the functionality of CEGIS
shrin18 opened this issue · comments
Following the paper words: “accepting the first RHS solutions that passes the check”. You use and implementation of CEGIS (the space explorer) (AliveDriver.cpp). So, there should be a way to able to find the place where you stop the exploration and then change it to continue the report of solutions with increasing cost. Currently the code in our pipeline gives us the RHS single candidate :
../../souper/build/souper-check -z3-path='../../souper/third_party/z3/build/z3' -infer-rhs -souper-infer-iN ${name}.lhsopt > ${name}.rhsopt
But we want to extend it to multiple candidates to perform further optimisations.