diff options
author | Arnaud Charlet <charlet@adacore.com> | 2021-03-01 05:45:25 -0500 |
---|---|---|
committer | Pierre-Marie de Rodat <derodat@adacore.com> | 2021-06-15 06:19:14 -0400 |
commit | 81e68a1954366f6b1730d75c932814121d743aa3 (patch) | |
tree | b66305227a77d8647e736d618980b8474147ab37 /gcc/ada/exp_ch8.adb | |
parent | 4dbdeeb889dfd4dcce214e1525b56a7464128a3c (diff) | |
download | gcc-81e68a1954366f6b1730d75c932814121d743aa3.zip gcc-81e68a1954366f6b1730d75c932814121d743aa3.tar.gz gcc-81e68a1954366f6b1730d75c932814121d743aa3.tar.bz2 |
[Ada] Rename Ada 202* to Ada 2022
gcc/ada/
* einfo.ads, errout.adb, errout.ads, exp_aggr.adb, exp_ch5.adb,
exp_ch6.adb, exp_ch8.adb, exp_ch9.adb, exp_imgv.adb,
exp_put_image.adb, fe.h, impunit.adb, impunit.ads,
libgnat/a-cobove.ads, libgnat/a-convec.ads, opt.ads,
par-ch12.adb, par-ch3.adb, par-ch4.adb, par-ch5.adb,
par-ch6.adb, par-prag.adb, par-util.adb, scans.ads, scng.adb,
sem_aggr.adb, sem_attr.adb, sem_ch10.adb, sem_ch12.adb,
sem_ch13.adb, sem_ch3.adb, sem_ch5.adb, sem_ch6.adb,
sem_ch8.adb, sem_elab.adb, sem_eval.adb, sem_prag.adb,
sem_res.adb, sem_type.adb, sem_util.adb, sem_util.ads,
sinfo.ads, snames.ads-tmpl, sprint.adb, switch-c.adb, usage.adb,
doc/gnat_ugn/building_executable_programs_with_gnat.rst,
doc/gnat_rm/implementation_defined_aspects.rst,
gcc-interface/trans.c: Update all references to Ada 2020 to Ada
2022. Rename pragma Ada_2020 to Ada_2022. Update documentation
accordingly.
* gnat_ugn.texi, gnat_rm.texi: Regenerate.
Diffstat (limited to 'gcc/ada/exp_ch8.adb')
-rw-r--r-- | gcc/ada/exp_ch8.adb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/ada/exp_ch8.adb b/gcc/ada/exp_ch8.adb index a50c8ed..dba21ed 100644 --- a/gcc/ada/exp_ch8.adb +++ b/gcc/ada/exp_ch8.adb @@ -76,7 +76,7 @@ package body Exp_Ch8 is -- clause applies (that can specify an arbitrary bit boundary), or where -- the enclosing record itself has a non-standard representation. - -- In Ada 2020, a third case arises when the renamed object is a nonatomic + -- In Ada 2022, a third case arises when the renamed object is a nonatomic -- subcomponent of an atomic object, because reads of or writes to it must -- access the enclosing atomic object. That's also the case for an object -- subject to the Volatile_Full_Access GNAT aspect/pragma in any language |