aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorPiotr Trojanek <trojanek@adacore.com>2022-01-05 16:40:44 +0100
committerPierre-Marie de Rodat <derodat@adacore.com>2022-01-11 13:24:48 +0000
commit13c0bf611a0f8dc73ac5ac463fcc6974eb55ae28 (patch)
treed2b1211b06b6622691c618a2874d1d8dcb3b2563 /gcc
parent4566dbce02a2c7d1334ab1a28ff92ade5768baad (diff)
downloadgcc-13c0bf611a0f8dc73ac5ac463fcc6974eb55ae28.zip
gcc-13c0bf611a0f8dc73ac5ac463fcc6974eb55ae28.tar.gz
gcc-13c0bf611a0f8dc73ac5ac463fcc6974eb55ae28.tar.bz2
[Ada] Balance parentheses in comments about allocators
gcc/ada/ * sem_ch4.adb (Analyze_Allocator): Fix comment. * sem_eval.ads (Compile-Time Known Values): Likewise.
Diffstat (limited to 'gcc')
-rw-r--r--gcc/ada/sem_ch4.adb4
-rw-r--r--gcc/ada/sem_eval.ads2
2 files changed, 3 insertions, 3 deletions
diff --git a/gcc/ada/sem_ch4.adb b/gcc/ada/sem_ch4.adb
index 42547e3..c916c21 100644
--- a/gcc/ada/sem_ch4.adb
+++ b/gcc/ada/sem_ch4.adb
@@ -515,7 +515,7 @@ package body Sem_Ch4 is
-- parameters. Note that this is now a static error even if the
-- subprogram is not the main program (this is a change, in an
-- earlier version only the main program was affected, and the
- -- check had to be done in the binder.
+ -- check had to be done in the binder).
if Nkind (P) = N_Subprogram_Body
and then Nkind (Parent (P)) = N_Compilation_Unit
@@ -563,7 +563,7 @@ package body Sem_Ch4 is
Find_Type (Subtype_Mark (E));
-- Analyze the qualified expression, and apply the name resolution
- -- rule given in 4.7(3).
+ -- rule given in 4.7(3).
Analyze (E);
Type_Id := Etype (E);
diff --git a/gcc/ada/sem_eval.ads b/gcc/ada/sem_eval.ads
index eb919f1..4fdd5a1 100644
--- a/gcc/ada/sem_eval.ads
+++ b/gcc/ada/sem_eval.ads
@@ -113,7 +113,7 @@ package Sem_Eval is
-- The expression 'C' is not static in the technical RM sense, but for many
-- simple record types, the size is in fact known at compile time. When we
-- are trying to perform compile time constant folding (for instance for
- -- expressions like C + 1, Is_Static_Expression or Is_OK_Static_Expression
+ -- expressions like C + 1), Is_Static_Expression or Is_OK_Static_Expression
-- are not the right functions to test if folding is possible. Instead, we
-- use Compile_Time_Known_Value. All static expressions that do not raise
-- constraint error (i.e. those for which Is_OK_Static_Expression is true)