Skip to content
/ smack Public
forked from smackers/smack

SMACK Software Verifier and Verification Toolchain

License

Notifications You must be signed in to change notification settings

Luweicai/smack

 
 

Repository files navigation

master branch ci status develop branch ci status

SMACK Logo

SMACK is both a modular software verification toolchain and a self-contained software verifier. It can be used to verify the assertions in its input programs. In its default mode, assertions are verified up to a given bound on loop iterations and recursion depth; it contains experimental support for unbounded verification as well. SMACK handles complicated feature of the C language, including dynamic memory allocation, pointer arithmetic, and bitwise operations.

Under the hood, SMACK is a translator from the LLVM compiler's popular intermediate representation (IR) into the Boogie intermediate verification language (IVL). Sourcing LLVM IR exploits an increasing number of compiler front-ends, optimizations, and analyses. Currently SMACK only supports the C language via the Clang compiler, though we are working on providing support for additional languages. Targeting Boogie exploits a canonical platform which simplifies the implementation of algorithms for verification, model checking, and abstract interpretation. Currently, SMACK leverages the Boogie and Corral verifiers.

See below for system requirements, installation, usage, and everything else.

We are very interested in your experience using SMACK. Please do contact Zvonimir or Michael with any possible feedback.

Support

  • For general questions, first consult the FAQ.

  • If something is otherwise broken or missing, open an issue.

  • As a last resort, send mail to Michael, Zvonimir, or both.

  • To stay informed about updates, you can either watch SMACK's Github page, or you can join SMACK's Google Group mailing list. Even without a Google account, you may join by sending mail to [email protected].

Acknowledgements

SMACK project has been partially supported by funding from the National Science Foundation, VMware, Amazon, and Microsoft Research. We also rely on University of Utah's Emulab infrastructure for extensive benchmarking of SMACK.

Table of Contents

  1. System Requirements and Installation
  2. Running SMACK
  3. Demos
  4. FAQ
  5. Inline Boogie Code
  6. Contribution Guidelines
  7. Projects
  8. Publications
  9. People

About

SMACK Software Verifier and Verification Toolchain

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 86.0%
  • C++ 9.3%
  • Python 2.9%
  • Rust 1.2%
  • Shell 0.4%
  • CMake 0.2%