How viperproject/boogie-proofgen works
Project type and purpose
• This is an open-source verification tool: a fork of the Boogie verifier extended with a proof-generation backend for Isabelle/HOL. It behaves like a compiler pipeline, taking a Boogie program through parsing, transformation, VC generation, SMT solving, and then emitting Isabelle proof scripts.
High-level architecture from the file structure
• Top-level directories
• Source/ — the main C# solution (Boogie.sln) with subprojects for each phase.
• ProofGenerationBenchmarks/ — sample Boogie programs and benchmarks.
• Test/ — regression tests driving BoogieDriver and comparing outputs.
• Util/ & etc/ — scripting, snippets, VM setup.
• Key subprojects under Source/ (each a .csproj)
• BoogieDriver — the CLI entry point.
• Core — AST, parser, scanner, command-line options, control-flow ID mapping.
• AbsInt, BaseTypes, Concurrency, Model, Predication, Graph, Houdini, Isabelle — support libraries for abstract interpretation, type systems, concurrency checking, model extraction, etc.
• ExecutionEngine — orchestration of runs, thread/task scheduling, result caching.
• VCExpr, VCGeneration — building verification conditions (VCs) and interacting with solvers.
• Provers/SMTLib — launching and communicating with external SMT solvers (e.g., Z3).
• ProofGeneration — the new extension that hooks into various transformation phases to collect data and generate Isabelle theories.