SPARK

This repository contains the source code for the SPARK project. SPARK is a software development technology specifically designed for engineering high-reliability applications. It consists of a programming language, a verification toolset and a design method which, taken together, ensure that ultra-low defect software can be deployed in application domains where high-reliability must be assured and where safety and security are key requirements. This repository provides visibility on the development process. The main line of development is in line with the development version of GNAT, which is not directly visible to the public (although patches are regularly transferred to the FSF repository at svn://gcc.gnu.org/svn/gcc/trunk/gcc/ada ), and it will probably be impossible to build the master branch of the software with any other compiler. However, buildable branches are provided corresponding to public compiler releases or the head of the FSF repository, see the section on Building SPARK below. SPARK is commercially supported by AdaCore and Capgemini, you can visit the AdaCore website for more information. You can download a "gnatprove" package from this github project. Extracting the package and adding the bin directory to your PATH is enough. You can get the GNAT compiler from the same link, and there is a different project for GNATStudio, the IDE. You can obtain SPARK via Alire. To do this, follow the installation instructions of Alire, then you can add the gnatprove dependency to an alire project using There is an older community version of the tools, packaged with GNAT and GNATStudio. You can download it from AdaCore's website. SPARK is led by AdaCore and co-developed by AdaCore, Capgemini and Inria. The SPARK team at AdaCore is responsible for the technology roadmap, taking into account the needs of all stakeholders: sales and marketing, customers, other development teams, community. The team is organized around a set of roles for QA, integration, certification, language evolution, etc. with two roles managing interactions: Defines the technology roadmap with all stakeholders. Coordinates and organizes the work in the team. Adjusts efforts and priorities based on the technology roadmap. Provides and maintains deep knowledge of the technology. Is the main reference point for knowledge on the technology. Is the software architect on the technology. Currently these roles are exercised by Claire Dross (Team Coordinator) and Johannes Kanig (Team Technical Authority). News about SPARK project are shared primarily on AdaCore's blog. Discussions about SPARK occur on a public mailing-list. You can find the definition of the SPARK language in the SPARK Reference Manual, and instructions on how to use the tool, together with a tutorial, in the SPARK User's Guide. SPARK sources are tied to the sources of GNAT compiler frontend. For this reason, you should use a compiler built from sources with a date matching the sources of SPARK. There are two options. To build SPARK with GNAT Community compiler, you need to use the corresponding branch of this repository. For example, to build with GNAT Community 2020, use the branch gpl-2020, as follows: SPARK repository uses submodules to keep in sync with corresponding versions of Why3, Alt-Ergo, CVC4 and Z3, which generally track the main repositories for these tools with minor modifications for the integration with SPARK. To retrieve the corresponding branch of these submodules, do: Since most of the source code is written in Ada an editor or IDE that has dedicated support for Ada is recommended. Below are tips for some common IDEs. The folder .vscode contains some settings and a README file that can be helpful when using VS Code.