diff options
author | Yannick Moy <moy@adacore.com> | 2022-11-25 17:16:06 +0100 |
---|---|---|
committer | Marc Poulhiès <poulhies@adacore.com> | 2022-12-06 14:58:49 +0100 |
commit | 400d9fc1f04336118c3200e2af14a620e7ea1d95 (patch) | |
tree | e5b73af6d4bb71aa52f994f402185f086e2df957 /maintainer-scripts | |
parent | 7dc44f280e7d1126b4d05e79c53b40df1afe334a (diff) | |
download | gcc-400d9fc1f04336118c3200e2af14a620e7ea1d95.zip gcc-400d9fc1f04336118c3200e2af14a620e7ea1d95.tar.gz gcc-400d9fc1f04336118c3200e2af14a620e7ea1d95.tar.bz2 |
ada: Allow No_Caching on volatile types
SPARK RM now allow the property No_Caching on volatile types, to
indicate that they should be considered volatile for compilation, but
not by GNATprove's analysis.
gcc/ada/
* contracts.adb (Add_Contract_Item): Allow No_Caching on types.
(Check_Type_Or_Object_External_Properties): Check No_Caching.
Check that non-effectively volatile types does not contain an
effectively volatile component (instead of just a volatile
component).
(Analyze_Object_Contract): Remove shared checking of No_Caching.
* sem_prag.adb (Analyze_External_Property_In_Decl_Part): Adapt checking
of No_Caching for types.
(Analyze_Pragma): Allow No_Caching on types.
* sem_util.adb (Has_Effectively_Volatile_Component): New query function.
(Is_Effectively_Volatile): Type with Volatile and No_Caching is not
effectively volatile.
(No_Caching_Enabled): Remove assertion to apply to all entities.
* sem_util.ads: Same.
Diffstat (limited to 'maintainer-scripts')
0 files changed, 0 insertions, 0 deletions