Cristian Cadar

OK, looks like we're ready to move to C++17!

@251 I took another look at this PR, and it looks good, except that it changes the default SAT solver in STP. Given that STP developers seem to be keen...

You are right, but I would do that separately, we can open an issue about it. For this issue, I think it's enough to give priority to CMS. If users...

We should only warn if the SAT solver is changed explicitly. Otherwise we should just report what SAT solver is used.

Perfect! But can I ask you to also document this at https://klee.github.io/docs/solver-chain/#stp ?

Thanks, again!

Let's close this inactive PR. I added a note at https://github.com/klee/klee/issues/678 about the missing support for these intrinsics.

My bad for not getting back to the PR. What I'd like to see is this being guarded by an option and documentation added to the website, as different concretization...

Thanks once again, @mishok2503. I have finally followed up on this in #1696. Together with #1407, that should lead to a more robust interaction with external calls.

This has now been fixed in KLEE 3.1, more exactly via #1696