{"id":170110,"date":"2008-12-10T11:07:20","date_gmt":"2008-12-10T11:07:20","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/research\/project\/vcc-a-verifier-for-concurrent-c\/"},"modified":"2018-04-03T16:39:58","modified_gmt":"2018-04-03T23:39:58","slug":"vcc-a-verifier-for-concurrent-c","status":"publish","type":"msr-project","link":"https:\/\/www.microsoft.com\/en-us\/research\/project\/vcc-a-verifier-for-concurrent-c\/","title":{"rendered":"VCC: A Verifier for Concurrent C"},"content":{"rendered":"

\"VCC<\/span><\/span>VCC is a tool that proves correctness of annotated concurrent C programs or finds problems in them. VCC extends C with design by contract features, like pre- and postcondition as well as type invariants. Annotated programs are translated to logical formulas using the Boogie tool, which passes them to an automated SMT solver Z3 to check their validity.<\/p>\n

\n

VCC is available for non-commercial use, with sources, at our codeplex site<\/a>.<\/p>\n<\/div>\n

 <\/p>\n

 <\/p>\n

\n

Workflow<\/h1>\n

The work flow is illustrated by the figure below. One starts with annotating the C code with contracts. Contracts are written using C preprocessor macros, so one can get rid of them using a single preprocessor switch and compile the code using one’s favorite C compiler. If the contracts are left in place, VCC when run on a program will report:<\/p>\n