diff options
| author | Piotr Trojanek <trojanek@adacore.com> | 2019-07-04 08:05:27 +0000 |
|---|---|---|
| committer | Pierre-Marie de Rodat <pmderodat@gcc.gnu.org> | 2019-07-04 08:05:27 +0000 |
| commit | d8be36d2873dd1cf9586790ff6c91dc17f37daa6 (patch) | |
| tree | a214c57ccdb62bcbd45ac510a4760f3b80687ef3 /gcc/ada/inline.adb | |
| parent | a0766a8258f014ac2715d8c49fcaf83b3eb62a00 (diff) | |
| download | gcc-d8be36d2873dd1cf9586790ff6c91dc17f37daa6.zip gcc-d8be36d2873dd1cf9586790ff6c91dc17f37daa6.tar.gz gcc-d8be36d2873dd1cf9586790ff6c91dc17f37daa6.tar.bz2 | |
[Ada] Keep assertions in internal units enabled for GNATprove
In GNATprove mode the assertion policy is now always enabled, even when
analysing internal units. Otherwise, assertion expressions (e.g.
Default_Initial_Condition) in internal units (e.g. Ada.Text_IO)
disappear in the semantic analysis phase of the frontend and the
GNATprove backend can't see them.
No frontend test provided, because only the GNATprove backend is
affected (and there appear to be no difference in the output with -gnatG
switch, because the expansion of Default_Initial_Condition is not
attached to the AST).
2019-07-04 Piotr Trojanek <trojanek@adacore.com>
gcc/ada/
* opt.adb (Set_Config_Switches): Keep assertions policy as
enabled when analysing internal units in GNATprove mode.
From-SVN: r273048
Diffstat (limited to 'gcc/ada/inline.adb')
0 files changed, 0 insertions, 0 deletions