-
Implement infrastructure to parse Horn clauses from a File/String. The parsing method should be part of `jayhorn.solver.Prover` and produce actual `ProverExpr`. It also should work with Eldarica and …
-
Spacer back-end currently does not respect the set time-out.
-
Extern functions include implications. This results in non-Horn clauses being output which Z3 does not handle correctly.
-
Need to develop a rule language (most likely based on Horn clauses), and parse into rules.
quoll updated
8 years ago
-
I would like us to tune the high level story of the paper a little. One way is to sell this just as "better rule injection". Another is to think more about "Reasoning with Low Rank Representations", o…
-
In the cfg, we have the information that if variable is constant or unique. However, this is not used when encoding things as Horn. Hence, we fail to verify the following program:
``` java
class A {
…
-
As Philipp pointed out, the handling of subtype invariants in the translation of pull may be unsound because currently, for a class hierarchy with A extends B extends C, we translate pull statements i…
-
The axioms that are generated for the type hierarchy seem to be broken:
https://github.com/jayhorn/jayhorn/blob/atva_memory_encoding/jayhorn/src/main/java/jayhorn/checker/Checker.java
(note that we'r…
-
Shouldn't reve be able to handle endless loops?
The horn clauses for the following programs are sat, which should not be the case.
``` c
extern int __mark(int i);
int foo(){
int i = 0;
int …
-
DISCLAIMER : Any similarity to anyone's presidential campaign slogan is purely coincidental.
tl;dr:
(1) what the hell is going on
(2) now the days have changed
(3) get rid of that ugly {{...}} guy…