aboutsummaryrefslogtreecommitdiff
path: root/gcc/ada/a-exexpr-gcc.adb
diff options
context:
space:
mode:
authorRalf Wildenhues <Ralf.Wildenhues@gmx.de>2008-03-24 17:48:07 +0000
committerRalf Wildenhues <rwild@gcc.gnu.org>2008-03-24 17:48:07 +0000
commit8fc789c82e053517281e28e141f8832d5c2f7f6e (patch)
tree89b2171703528d83f5a20ddb5bbf2e0adb78a9ad /gcc/ada/a-exexpr-gcc.adb
parent01b119402f3f7e1edf6e72ad00499ba1ff80cb8e (diff)
downloadgcc-8fc789c82e053517281e28e141f8832d5c2f7f6e.zip
gcc-8fc789c82e053517281e28e141f8832d5c2f7f6e.tar.gz
gcc-8fc789c82e053517281e28e141f8832d5c2f7f6e.tar.bz2
9drpc.adb, [...]: Fix comment typos.
2008-03-24 Ralf Wildenhues <Ralf.Wildenhues@gmx.de> * 9drpc.adb, a-caldel-vms.adb, a-caldel.adb, a-calend-vms.adb, a-calend.adb, a-calend.ads, a-calfor.adb, a-chahan.ads, a-chtgke.adb, a-cihama.ads, a-ciorse.adb, a-clrefi.ads, a-cohama.ads, a-comlin.ads, a-coorse.adb, a-crbtgk.adb, a-direct.adb, a-except-2005.adb, a-except-2005.ads, a-except.adb, a-except.ads, a-exexda.adb, a-exexpr-gcc.adb, a-exexpr.adb, a-exextr.adb, a-filico.ads, a-finali.ads, a-intnam-aix.ads, a-intnam-solaris.ads, a-ngcefu.adb, a-ngelfu.adb, a-numaux-darwin.adb, a-numeri.ads, a-sequio.ads, a-strbou.ads, a-strfix.adb, checks.adb, exp_ch3.adb, exp_ch4.adb, exp_ch4.ads, exp_ch5.adb, exp_ch6.adb, exp_ch6.ads, exp_ch7.adb, exp_ch7.ads, exp_ch9.adb, exp_ch9.ads, exp_dbug.adb, exp_dbug.ads, exp_disp.adb, exp_dist.adb, exp_dist.ads, exp_fixd.adb, exp_fixd.ads: Fix comment typos. From-SVN: r133483
Diffstat (limited to 'gcc/ada/a-exexpr-gcc.adb')
-rw-r--r--gcc/ada/a-exexpr-gcc.adb14
1 files changed, 7 insertions, 7 deletions
diff --git a/gcc/ada/a-exexpr-gcc.adb b/gcc/ada/a-exexpr-gcc.adb
index c27c31a..ae6e0f7 100644
--- a/gcc/ada/a-exexpr-gcc.adb
+++ b/gcc/ada/a-exexpr-gcc.adb
@@ -47,7 +47,7 @@ package body Exception_Propagation is
-- These come from "C++ ABI for Itanium: Exception handling", which is
-- the reference for GCC. They are used only when we are relying on
- -- back-end tables for exception propagation, which in turn is currenly
+ -- back-end tables for exception propagation, which in turn is currently
-- only the case for Zero_Cost_Exceptions in GNAT5.
-- Return codes from the GCC runtime functions used to propagate
@@ -132,7 +132,7 @@ package body Exception_Propagation is
Id : Exception_Id;
-- GNAT Exception identifier. This is filled by Propagate_Exception
-- and then used by the personality routine to determine if the context
- -- it examines contains a handler for the exception beeing propagated.
+ -- it examines contains a handler for the exception being propagated.
N_Cleanups_To_Trigger : Integer;
-- Number of cleanup only frames encountered in SEARCH phase. This is
@@ -160,8 +160,8 @@ package body Exception_Propagation is
-- by the personality routine through the accessors declared below. Ada
-- specific fields are thus always accessed through consistent layout, and
-- we expect the actual alignment to always be large enough to avoid traps
- -- from the C accesses to the common header. Besides, accessors aleviate
- -- the need for a C struct whole conterpart, both painful and errorprone
+ -- from the C accesses to the common header. Besides, accessors alleviate
+ -- the need for a C struct whole counterpart, both painful and error-prone
-- to maintain anyway.
type GNAT_GCC_Exception_Access is access all GNAT_GCC_Exception;
@@ -670,7 +670,7 @@ package body Exception_Propagation is
-----------
-- The current model implemented for the stack of occurrences is a
- -- simplification of previous attempts, which all prooved to be flawed or
+ -- simplification of previous attempts, which all proved to be flawed or
-- would have needed significant additional circuitry to be made to work
-- correctly.
@@ -685,7 +685,7 @@ package body Exception_Propagation is
-- interface.
-- The basic point is that arranging for an occurrence to always appear at
- -- most once on the stack requires a way to determine if a given occurence
+ -- most once on the stack requires a way to determine if a given occurrence
-- is already there, which is not as easy as it might seem.
-- An attempt was made to use the Private_Data pointer for this purpose.
@@ -725,7 +725,7 @@ package body Exception_Propagation is
-- but making this to work while still avoiding memory leaks is far
-- from trivial.
- -- The current scheme has the advantage of beeing simple, and induces
+ -- The current scheme has the advantage of being simple, and induces
-- extra costs only in reraise cases which is acceptable.
end Exception_Propagation;