Datalog-Based Binary Equivalence

Summary

DALEQ - Datalog-based Binary Equivalence Publications Build and Use CLI DALEQ has been developed and tested with Java 17. DALEQ can be built with Maven as follows: mvn clean package dependency:copy-dependencies Then run DALEQ as follows (for windows: change the classpath separator accordingly): java -DSOUFFLE=<path-to-souffle> -cp "target/classes:target/dependency/*" io.github.bineq.daleq.cli.Main \ -j1,--jar1 <arg> the first jar file to compare (required) -j2,--jar2 <arg> the second jar file to compare (required) -o,--out <arg> the output folder where the report will be generated (required) -s1,--src1 <arg> the first jar file with source code to compare (optional) -s2,--src2 <arg> the second jar file with source code to compare (optional) -a,--autoopen if set, the generated html report will be opened automatically (dont use for CLI integration) The jar built can also be used directly as an executable superjar. java -DSOUFFLE=<path-to-souffle> -jar target/daleq-<daleq-version>.jar \ -j1,--jar1 <arg> the first jar file to compare (required) -j2,--jar2 <arg> the second jar file to compare (required) -o,--out <arg> the output folder where the report will be generated (required) -s1,--src1 <arg> the first jar file with source code to compare (optional) -s2,--src2 <arg> the second jar file with source code to compare (optional) -a,--autoopen if set the generated html report will be opened automatically (dont use for CLI integration) Running the program will create a report report.html in the specified output folder. The program returns with the following exit codes: 0 - all classes and resources are equal, source codes (if analysed) are equivalent 1 - some classes are not equal but still equivalent, resources are equal, source-codes (if analysed) are equivalent 2 - some classes are not equivalent (wrt daleq) or some resources (e.g. metadata) are not equal or some sources (if analysed) are not equivalent This can be used to integrate the tool into CI processes. Overview D...