diff options
| author | Kazu Hirata <kazu@codesourcery.com> | 2006-05-28 18:03:28 +0000 |
|---|---|---|
| committer | Kazu Hirata <kazu@gcc.gnu.org> | 2006-05-28 18:03:28 +0000 |
| commit | ce2e12c27eebde4eedb1b95f69cda8662bf9ee3d (patch) | |
| tree | 476907f2cf934fdc4751893878c1d3f0fa3b64c3 /gcc/ada/trans.c | |
| parent | e2ae1407d3a0429fada6ff23f38ebf96bd62bd73 (diff) | |
| download | gcc-ce2e12c27eebde4eedb1b95f69cda8662bf9ee3d.zip gcc-ce2e12c27eebde4eedb1b95f69cda8662bf9ee3d.tar.gz gcc-ce2e12c27eebde4eedb1b95f69cda8662bf9ee3d.tar.bz2 | |
decl.c, [...]: Fix comment typos.
* decl.c, env.c, gigi.h, init.c, initialize.c, raise-gcc.c,
sem_ch13.adb, sysdep.c, targtyps.c, tb-alvxw.c, tracebak.c,
trans.c, utils.c: Fix comment typos. Follow spelling
conventions.
* gnat_rm.texi, gnat_ugn.texi, : Fix typos. Follow spelling
conventions.
From-SVN: r114171
Diffstat (limited to 'gcc/ada/trans.c')
| -rw-r--r-- | gcc/ada/trans.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/ada/trans.c b/gcc/ada/trans.c index 30c0fb5..b7b3598 100644 --- a/gcc/ada/trans.c +++ b/gcc/ada/trans.c @@ -1510,7 +1510,7 @@ Subprogram_Body_to_gnu (Node_Id gnat_node) we must turn a condition into the corresponding exception even if there is no applicable Ada handler, and need at least one condition handler per possible call chain involving GNAT code. OTOH, establishing the handler - has a cost so we want to mimize the number of subprograms into which this + has a cost so we want to minimize the number of subprograms into which this happens. The foreign or exported condition is expected to satisfy all the constraints. */ if (TARGET_ABI_OPEN_VMS @@ -4829,7 +4829,7 @@ gnat_gimplify_stmt (tree *stmt_p) /* The reason for this routine's existence is two-fold. First, with some debugging formats, notably MDEBUG on SGI IRIX, the linker will remove duplicate debugging information if two - clients have identical debugguing information. With the normal scheme + clients have identical debugging information. With the normal scheme of elaboration, this does not usually occur, since entities in with'ed packages are elaborated on demand, and if clients have different usage patterns, the normal case, then the order and selection of entities |