VerCors Verification Toolset
This repository hosts VerCors, a toolset for the verification of concurrent and parallel programs. VerCors aims to verify many different concurrency constructs, including: heterogeneous concurrency (Java and C), GPU kernels using barriers and atomics (OpenCL), and compiler directives as used in deterministic parallelism (OpenMP). VerCors is able to prove data-race freedom, memory safety, and functional correctness of (concurrent) programs written in Java, C, OpenCL, OpenMP, and PVL (Prototypal Verification Language, a procedural toy language for prototyping new verification features). Moreover, VerCors is designed to be language-independent, which makes adding new front-end languages a straightforward engineering effort.
A list of verified examples and case studies is maintained online and can be found here. This webpage also contains an online interface for VerCors and allows to try VerCors online.
The VerCors toolset can be installed and used on MacOS X, Linux, and Windows (via Cygwin). When using Windows make sure that the environment variable
JAVA_HOME is configured. A basic installation requires:
- Oracle Java Development Kit (JDK), version 8 (the current version of VerCors does not work with Java 9!)
- Git (on Windows you need Git Bash, see https://git-scm.com/downloads)
- Apache Ant, version 1.10.3 (see http://ant.apache.org for instructions)
- Apache Commons (from https://commons.apache.org/proper/commons-lang/)
- Scala SBT, version 1.1.4 (see http://www.scala-sbt.org for instructions)
- clang (see https://clang.llvm.org/)
If you have these requirements, proceed to 'Building'. On MacOS X, the easiest way to get them is:
- Be sure to have installed Homebrew
- brew tap homebrew/cask-versions
- brew cask install java8
- brew install ant
- Rest of the instructions below
For a basic build of VerCors the following steps should be taken:
- Clone the VerCors repository using
git clone https://github.com/utwente-fmt/vercors.gitand move into the cloned directory,
- Build VerCors with Ant by running
ant clean, followed by
- Test whether the build was successful by running
./unix/bin/vct --test=examples/manual --tool=silicon --lang=pvl,java.
The last command tests the VerCors installation by verifying a large collection of examples (from the
./examples directory). This command should eventually report that
all ? tests passed.
VerCors verifies programs that are annotated with JML-style specifications (the underlying theory uses separation logic with permission accounting). Details on the specification language can be found on the VerCors Wiki pages. Furthermore, a large collection of example programs can be found (and verified) in the
The VerCors toolset can be used from the main directory by running
./unix/bin/vct --silver=silicon <filepath>, with
<filepath> the path of the (Java, C, or PVL) file to verify.
- For questions and support, email to email@example.com.
- For bug reports and feature requests, visit https://github.com/utwente-fmt/vercors/issues.
A complete list of papers on the VerCors project is given here.
Copyright (c) 2008 - 2018 Formal Methods and Tools, University of Twente All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the University of Twente nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.