Name | Date | Size | ||
---|---|---|---|---|
.. | 25-Jul-2019 | 8 | ||
doit | H A D | 25-Jul-2019 | 1.3 KiB | |
gold/ | H | 25-Jul-2019 | 4 | |
README | H A D | 25-Jul-2019 | 1.2 KiB |
README
1Our round-trip testing can be done here. 2 3For now, we only go from ACL2 source file axioms.lisp to an ML 4version. 5 6We currently create two files in results/: an "essential" version of 7ACL2 source file axioms.lisp, and the result of translating 8gold/axioms.lisp to axioms.ml. We tend to trust the translation to an 9"essential" axioms.lisp. 10 11Instructions for updating when ACL2 version changes: 12 13When ACL2 is updated to a new version, first run doit. Then check 14quickly that results/axioms.lisp and gold/axioms.lisp are similar and 15that gold/axioms.ml and results/axioms.ml (the latter generated from 16gold/axioms.lisp) are identical. This can perhaps be determined 17easily by inspection of ./diffout. 18 19diff gold/axioms.ml results/axioms.ml 20# The above should produce no output, because results/axioms.ml was 21# generated from gold/axioms.lisp. 22cp -p results/axioms.lisp gold/ 23./doit 24diff gold/axioms.lisp results/axioms.lisp 25# The above should produce no output. 26# Since axioms.ml was OK before, we figure that it's OK now as well: 27cp -p results/axioms.ml gold/ 28# Now do final check, which should succeed: 29./doit 30# Then commit to svn (preferably stating the ACL2 version): 31svn commit -m 'Updated for new ACL2 version' 32