ANSI/ISO C Specification Language
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
| Paradigm | declarative with few imperative features. |
|---|---|
| Designed by | Commissariat à l'Énergie Atomique and INRIA |
| Developer | Commissariat à l'Énergie Atomique and INRIA |
| First appeared | 2008 |
| Stable release | v1.16
/ 19 November 2020 |
| Typing discipline | static |
| Major implementations | |
| Frama-C | |
| Influenced by | |
| JML | |
The ANSI/ISO C Specification Language (ACSL) is a specification language for C programs, using Hoare style pre- and postconditions and invariants, that follows the design by contract paradigm. Specifications are written as C annotation comments to the C program, which hence can be compiled with any C compiler.
The current verification tool for ACSL is Frama-C. It also implements a sister language, ANSI/ISO C++ Specification Language (ACSL++), defined for C++.
Overview[edit]
In 1983, the American National Standards Institute (ANSI) commissioned a committee, X3J11, to standardize the C language. The first standard for C was published by ANSI. Although this document was subsequently adopted by International Organization for Standardization (ISO) and subsequent revisions published by ISO have been adopted by ANSI, the name ANSI C continues to be used.
ACSL is a behavioral interface specification language (BISL). It aims at specifying behavioral properties of C source code. The main inspiration for this language comes from the specification language of the Caduceus tool for deductive verification of behavioral properties of C programs. The specification language of Caduceus is itself inspired from JML which aims at similar goals for Java source code.
One difference with JML is that ACSL is intended for static verification and deductive verification whereas JML is designed both for runtime assertion checking and static verification using for instance the ESC/Java tool.
Syntax[edit]
Consider the following example for the prototype of a function named incrstar:
/*@ requires \valid(p);
@ assigns *p;
@ ensures *p == \old(*p) + 1;
@*/
void incrstar (int *p);
The contract is given by the comment which starts with /*@. Its meaning is as follows:
- the first line is a precondition: it states that function
incrstarmust be called with a pointerpthat points to a safely allocated memory location. - Second line is a frame clause, stating that function
incrstardoes not modify any memory location but the one pointed to byp. - Finally, the
ensuresclause is a postcondition, which specifies that the value*pis incremented by one.
A valid implementation of the above function would be:
void incrstar (int *p) {
(*p)++;
}
Tool support[edit]
Most of the features of ACSL are supported by Frama-C.
The TrustInSoft static analyzer is a commercial derivative of Frama-C. It verifies program behavior and (with builtin rules based on the language specification) catch instances of undefined behavior.[1]
References[edit]
- ^ "ACSL Properties". TrustInSoft Documentation 1.42-dev documentation.
- Example of ACSL usage Sufficient Preconditions for Modular Assertion Checking in VMCAI 2008 pages 188–202.
- ACSL by Example, a well-documented collection of ACSL specifications of simple algorithms has been developed by the VerificationGroup at Fraunhofer FOKUS
- A tutorial about Frama-C with WP and ACSL for beginners that also provides some ideas about the theory behind the tools (available also in French).
- A report on using ACSL and Frama-C to formulate and verify low-level requirements in the context of a DO-178C compliant project
- Report mentioning the use of ACSL in teaching [1], Петренко Ольга Леонидовна and Хорошилов Алексей Владимирович.
- At Technikum Wien ACSL and Frama-C are taught in a course on design and verification.
External links[edit]
- The complete ACSL specification is available from the download page of Frama-C.
- TSnippet from TrustInSoft allows for in-browser testing of C snippets using ACSL.