Skip to content

UCSD-PL/kraken

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
bin
 
 
dep
 
 
doc
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Reflex DSL: Automating Formal Proofs for Reactive Systems

This repository gives the source code for the project described at this page: http://goto.ucsd.edu/reflex/. A VM image is available at that web page for trying out the systems we built (web browser, SSH server, web server), running the proof automation, and building a kernel of your own using Reflex.

This document describes the structure of this repository.

Directory structure

The repository is structured as follows:

  • The implementation of the interpreter is located at reflex/coq. A description of some of the files under that directory is given at docs/source-docs.txt.

  • The kernels for the web browser, ssh server, and web server are located at reflex/coq/bench-quark/Kernel.reflex, reflex/coq/bench-ssh/Kernel.reflex, reflex/coq/bench-webserver/Kernel.reflex, respectively.

  • The implementation of the proof automation is also found in reflex/coq. The bulk of the automation implementation is, somewhat confusingly, in the file ReflexFrontend.v.

  • bin contains a script for running proof general with the appropriate arguments for this project.

  • dep contains a makefile for pulling in and compiling the library Ynot, which we build upon.

  • doc contains a description of the files in reflex/coq. It also contains a script for generating a dependency diagram for modules in this project and a slightly outdated diagram.

  • examples is deprecated.

  • All Ocaml code related to extracting our interpreter is located in reflex/ml. This includes the Ocaml implementations of all of our Reflex primitives (for making system calls).

  • reflex/c-stubs contains a C implementation for passing a file descriptor over a socket.

  • reflex/examples contains the implementations of components that communicate with the echo server kernel and that communicate with the web server kernel.

Compiling

Simply run make to build the interpreter. In order to build a particular kernel, place your kernel in reflex/coq/bench-<name>. Under that directory, run

ln -s ../Makefile.bench Makefile
cd ../../
make build NAME=<name>

The resulting binary will reside in reflex/coq/bench-<name>/ml/kernel.

Running the proof automation on our properties

cd reflex/coq
make bench BENCHOUT=<results-dir> TIMEOUT=<timeout>

A single file called /results.csv will be created, giving, for each property, the time taken to produce a proof (Ltac), the time taken to check the proof (Qed), and the maximum memory used while creating the proof.

You can also tweak the automation optimizations that are run by modifying Opt.v. This file consists of six boolean valued expressions, each corresponding to an optimization.

Make sure that when you run automation on a machine with at least 4GB of memory.

Running the proof automation on your properties

Enter the directory where the kernel resides. Run make policies.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published