summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2005-05-29 03:57:15 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2005-05-29 03:57:15 +0000
commit2e4ea0c900ac4062061c86d5cd41814adb84ef0e (patch)
tree2da0d7b83f595be76a4a27d1501d770959ab4e85
parentf85787e9114d8f75971b148580a221befa26e2c7 (diff)
downloadgcc-2e4ea0c900ac4062061c86d5cd41814adb84ef0e.tar.gz
* cal.c, decl.c, init.c, raise.c, trans.c, utils2.c: Fix
comment typos. * gnat_rm.texi, gnat_ugn.texi: Fix typos. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@100312 138bc75d-0d04-0410-961f-82ee72b054a4
-rw-r--r--gcc/ada/ChangeLog6
-rw-r--r--gcc/ada/cal.c4
-rw-r--r--gcc/ada/decl.c6
-rw-r--r--gcc/ada/gnat_rm.texi4
-rw-r--r--gcc/ada/gnat_ugn.texi10
-rw-r--r--gcc/ada/init.c10
-rw-r--r--gcc/ada/raise.c10
-rw-r--r--gcc/ada/trans.c6
-rw-r--r--gcc/ada/utils2.c2
9 files changed, 32 insertions, 26 deletions
diff --git a/gcc/ada/ChangeLog b/gcc/ada/ChangeLog
index a08251e21b0..b8c042c9d69 100644
--- a/gcc/ada/ChangeLog
+++ b/gcc/ada/ChangeLog
@@ -1,3 +1,9 @@
+2005-05-29 Kazu Hirata <kazu@cs.umass.edu>
+
+ * cal.c, decl.c, init.c, raise.c, trans.c, utils2.c: Fix
+ comment typos.
+ * gnat_rm.texi, gnat_ugn.texi: Fix typos.
+
2005-05-16 Nathanael Nerode <neroden@gcc.gnu.org>
PR ada/20270
diff --git a/gcc/ada/cal.c b/gcc/ada/cal.c
index 20a631634bb..283a0e6856e 100644
--- a/gcc/ada/cal.c
+++ b/gcc/ada/cal.c
@@ -32,8 +32,8 @@
/* This file contains those routines named by Import pragmas in package */
/* GNAT.Calendar. It is used to do Duration to timeval conversion. */
-/* These are simple wrappers function to abstarct the fact that the C */
-/* struct timeval fields type are not normalized (they are generaly */
+/* These are simple wrappers function to abstract the fact that the C */
+/* struct timeval fields type are not normalized (they are generally */
/* defined as int or long values). */
#if defined(VMS)
diff --git a/gcc/ada/decl.c b/gcc/ada/decl.c
index c881d55b41f..bd9f26017b5 100644
--- a/gcc/ada/decl.c
+++ b/gcc/ada/decl.c
@@ -839,7 +839,7 @@ gnat_to_gnu_entity (Entity_Id gnat_entity, tree gnu_expr, int definition)
}
/* If this is a pointer and it does not have an initializing
- expression, initialize it to NULL, unless the obect is
+ expression, initialize it to NULL, unless the object is
imported. */
if (definition
&& (POINTER_TYPE_P (gnu_type) || TYPE_FAT_POINTER_P (gnu_type))
@@ -4223,7 +4223,7 @@ elaborate_entity (Entity_Id gnat_entity)
Node_Id gnat_lb = Type_Low_Bound (gnat_entity);
Node_Id gnat_hb = Type_High_Bound (gnat_entity);
- /* ??? Tests for avoiding static constaint error expression
+ /* ??? Tests for avoiding static constraint error expression
is needed until the front stops generating bogus conversions
on bounds of real types. */
@@ -6322,7 +6322,7 @@ static int
compatible_signatures_p (tree ftype1, tree ftype2)
{
/* As of now, we only perform very trivial tests and consider it's the
- programmer's responsability to ensure the type correctness in the Ada
+ programmer's responsibility to ensure the type correctness in the Ada
declaration, as in the regular Import cases.
Mismatches typically result in either error messages from the builtin
diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi
index 6471f36a7a1..a985edc42d8 100644
--- a/gcc/ada/gnat_rm.texi
+++ b/gcc/ada/gnat_rm.texi
@@ -4818,7 +4818,7 @@ subprogram yields a value that can be called as long as the subprogram
is in scope (normal Ada 95 accessibility rules restrict this usage).
It is possible to use @code{Unrestricted_Access} for any type, but care
-must be excercised if it is used to create pointers to unconstrained
+must be exercised if it is used to create pointers to unconstrained
objects. In this case, the resulting pointer has the same scope as the
context of the attribute, and may not be returned to some enclosing
scope. For instance, a function cannot use @code{Unrestricted_Access}
@@ -12522,7 +12522,7 @@ collisions occur and each item can be retrieved from the table in one
probe (perfect property). The hash table size corresponds to the exact
size of the key set and no larger (minimal property). The key set has to
be know in advance (static property). The hash functions are also order
-preservering. If w2 is inserted after w1 in the generator, their
+preserving. If w2 is inserted after w1 in the generator, their
hashcode are in the same order. These hashing functions are very
convenient for use with realtime applications.
diff --git a/gcc/ada/gnat_ugn.texi b/gcc/ada/gnat_ugn.texi
index 7f4e0671f87..e27ed3de73c 100644
--- a/gcc/ada/gnat_ugn.texi
+++ b/gcc/ada/gnat_ugn.texi
@@ -12582,7 +12582,7 @@ Additionally, you may define the library-related attributes
@code{Library_Auto_Init}, @code{Library_Options} and @code{Library_GCC}.
The @code{Library_Name} attribute has a string value. There is no restriction
-on the name of a library. It is the responsability of the developer to
+on the name of a library. It is the responsibility of the developer to
choose a name that will be accepted by the platform. It is recommended to
choose names that could be Ada identifiers; such names are almost guaranteed
to be acceptable on all platforms.
@@ -12664,7 +12664,7 @@ if @file{a1.ads}, @file{a2.ads} or @file{a2.adb} includes a statement
@code{"with L1;"}.
To be sure that all the sources in the library associated with @code{L} are
-up to date, and that all the sources of parject @code{A} are also up to date,
+up to date, and that all the sources of project @code{A} are also up to date,
the following two commands needs to be used:
@smallexample
@@ -15221,7 +15221,7 @@ affected cases include:
@noindent
In compact mode (when GNAT style layout or compact layout is set),
the pretty printer uses one level of indentation instead
-of two. This is achived in the record definition and record representation
+of two. This is achieved in the record definition and record representation
clause cases by putting the @code{record} keyword on the same line as the
start of the declaration or representation clause, and in the block and loop
case by putting the block or loop header on the same line as the statement
@@ -16106,7 +16106,7 @@ all upper case). Characters of the other case are folded as required.
@var{length} represents the length of the krunched name. The default
when no argument is given is ^8^39^ characters. A length of zero stands for
unlimited, in other words do not chop except for system files where the
-impled crunching length is always eight characters.
+implied crunching length is always eight characters.
@noindent
The output is the krunched name. The output has an extension only if the
@@ -27062,7 +27062,7 @@ There is nothing specific to Windows in this area. @pxref{Library Projects}.
@end menu
@noindent
-Note that it is prefered to use the built-in GNAT DLL support
+Note that it is preferred to use the built-in GNAT DLL support
(@pxref{Building DLLs with GNAT}) or GNAT Project files
(@pxref{Building DLLs with GNAT Project files}) to build DLLs.
diff --git a/gcc/ada/init.c b/gcc/ada/init.c
index 12a9badafc2..7ca680040bd 100644
--- a/gcc/ada/init.c
+++ b/gcc/ada/init.c
@@ -277,10 +277,10 @@ __gnat_set_globals (int main_priority,
call chain. To evaluate if a handler applies at some point in this chain,
the propagation engine needs to determine what region the corresponding
call instruction pertains to. The return address may not be attached to the
- same region as the call, so the unwinder unconditionally substracts "some"
+ same region as the call, so the unwinder unconditionally subtracts "some"
amount to the return addresses it gets to search the region tables. The
exact amount is computed to ensure that the resulting address is inside the
- call instruction, and is thus target dependant (think about delay slots for
+ call instruction, and is thus target dependent (think about delay slots for
instance).
When we raise an exception from a signal handler, e.g. to transform a
@@ -1794,10 +1794,10 @@ __gnat_initialize (void *eh ATTRIBUTE_UNUSED)
constructor fashion, typically triggered by the VxWorks loader. This is
achieved by way of a special variable declaration in the crt object, the
name of which has been deduced by analyzing the output of the "munching"
- step documented for C++. The de-registration is handled symetrically,
+ step documented for C++. The de-registration is handled symmetrically,
a-la C++ destructor fashion and typically triggered by the dynamic
unloader. Note that since the tables shall be registered against a
- common datastructure, libgcc should be one of the modules (vs beeing
+ common datastructure, libgcc should be one of the modules (vs being
partially linked against all the others at build time) and shall be
loaded first.
@@ -1991,7 +1991,7 @@ __gnat_adjust_context_for_raise (int signo ATTRIBUTE_UNUSED,
{
/* The point is that the interrupted context PC typically is the address
that we should search an EH region for, which is different from the call
- return address case. The target independant part of the GCC unwinder
+ return address case. The target independent part of the GCC unwinder
don't differentiate the two situations, so we compensate here for the
adjustments it will blindly make.
diff --git a/gcc/ada/raise.c b/gcc/ada/raise.c
index d0abc8a79c0..626adfe74bf 100644
--- a/gcc/ada/raise.c
+++ b/gcc/ada/raise.c
@@ -264,7 +264,7 @@ db_phases (int phases)
table which heads a list of possible actions to be taken (see below).
If it is determined that indeed an action should be taken, that
- is, if one action filter matches the exception beeing propagated,
+ is, if one action filter matches the exception being propagated,
then control should be transfered to landing-pad.
A null first-action-index indicates that there are only cleanups
@@ -283,7 +283,7 @@ db_phases (int phases)
Non null action-filters provide an index into the ttypes [] table
(see below), from which information may be retrieved to check if it
- matches the exception beeing propagated.
+ matches the exception being propagated.
action-filter > 0 means there is a regular handler to be run,
@@ -302,7 +302,7 @@ db_phases (int phases)
A null value indicates a catch-all handler in C++, and an "others"
handler in Ada.
- Non null values are used to match the exception beeing propagated:
+ Non null values are used to match the exception being propagated:
In C++ this is a pointer to some rtti data, while in Ada this is an
exception id.
@@ -611,7 +611,7 @@ get_region_description_for (_Unwind_Context *uw_context,
typedef enum
{
/* Found some call site base data, but need to analyze further
- before beeing able to decide. */
+ before being able to decide. */
unknown,
/* There is nothing relevant in the context at hand. */
@@ -761,7 +761,7 @@ get_call_site_action_for (_Unwind_Context *uw_context,
{
_Unwind_Ptr ip
= _Unwind_GetIP (uw_context) - 1;
- /* Substract 1 because GetIP yields a call return address while we are
+ /* Subtract 1 because GetIP yields a call return address while we are
interested in information for the call point. This does not always yield
the exact call instruction address but always brings the ip back within
the corresponding region.
diff --git a/gcc/ada/trans.c b/gcc/ada/trans.c
index 869ce3f5603..394ea1b64a0 100644
--- a/gcc/ada/trans.c
+++ b/gcc/ada/trans.c
@@ -2316,7 +2316,7 @@ Exception_Handler_to_gnu_zcx (Node_Id gnat_node)
is integer_zero_node. It would not work, however, because GCC's
notion of "catch all" is stronger than our notion of "others". Until
we correctly use the cleanup interface as well, doing that would
- prevent the "all others" handlers from beeing seen, because nothing
+ prevent the "all others" handlers from being seen, because nothing
can be caught beyond a catch all from GCC's point of view. */
gnu_etypes_list = tree_cons (NULL_TREE, gnu_etype, gnu_etypes_list);
}
@@ -2431,7 +2431,7 @@ Compilation_Unit_to_gnu (Node_Id gnat_node)
If this is an expression, return the GCC equivalent of the expression. If
it is a statement, return the statement. In the case when called for a
statement, it may also add statements to the current statement group, in
- which case anything it returns is to be interpreted as occuring after
+ which case anything it returns is to be interpreted as occurring after
anything `it already added. */
tree
@@ -4261,7 +4261,7 @@ add_decl_expr (tree gnu_decl, Entity_Id gnat_entity)
}
}
- /* If this is a DECL_EXPR for a variable with DECL_INITIAl set,
+ /* If this is a DECL_EXPR for a variable with DECL_INITIAL set,
there are two cases we need to handle here. */
if (TREE_CODE (gnu_decl) == VAR_DECL && DECL_INITIAL (gnu_decl))
{
diff --git a/gcc/ada/utils2.c b/gcc/ada/utils2.c
index 6ca8b99e50a..ae56b421a32 100644
--- a/gcc/ada/utils2.c
+++ b/gcc/ada/utils2.c
@@ -176,7 +176,7 @@ known_alignment (tree exp)
case PLUS_EXPR:
case MINUS_EXPR:
/* If two address are added, the alignment of the result is the
- minimum of the two aligments. */
+ minimum of the two alignments. */
lhs = known_alignment (TREE_OPERAND (exp, 0));
rhs = known_alignment (TREE_OPERAND (exp, 1));
this_alignment = MIN (lhs, rhs);