diff options
| author | Piotr Trojanek <trojanek@adacore.com> | 2020-05-09 00:06:16 +0200 |
|---|---|---|
| committer | Pierre-Marie de Rodat <derodat@adacore.com> | 2020-07-15 09:42:38 -0400 |
| commit | 5f9afe0dc1c06cd7b004280d84e4cb31c8616894 (patch) | |
| tree | 03a7106e2f6a2c38245b2735880d0301a33652b7 /gcc/ada | |
| parent | 0b4034c06b376f1219925546eb1006a2627ca336 (diff) | |
| download | gcc-5f9afe0dc1c06cd7b004280d84e4cb31c8616894.zip gcc-5f9afe0dc1c06cd7b004280d84e4cb31c8616894.tar.gz gcc-5f9afe0dc1c06cd7b004280d84e4cb31c8616894.tar.bz2 | |
[Ada] Fix typo in "accommodate" in docs and comments
gcc/ada/
* doc/gnat_rm/representation_clauses_and_pragmas.rst: Fix typo.
* gnat_rm.texi: Regenerate.
* libgnat/s-secsta.ads (Memory_Alignment): Likewise.
Diffstat (limited to 'gcc/ada')
| -rw-r--r-- | gcc/ada/doc/gnat_rm/representation_clauses_and_pragmas.rst | 2 | ||||
| -rw-r--r-- | gcc/ada/gnat_rm.texi | 2 | ||||
| -rw-r--r-- | gcc/ada/libgnat/s-secsta.ads | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/gcc/ada/doc/gnat_rm/representation_clauses_and_pragmas.rst b/gcc/ada/doc/gnat_rm/representation_clauses_and_pragmas.rst index efcdc80..7bae014 100644 --- a/gcc/ada/doc/gnat_rm/representation_clauses_and_pragmas.rst +++ b/gcc/ada/doc/gnat_rm/representation_clauses_and_pragmas.rst @@ -582,7 +582,7 @@ that in each case the base is ``Short_Short_Integer`` with a size of 8): Note: the entries marked '*' are not actually specified by the Ada Reference Manual, which has nothing to say about size in the dynamic -case. What GNAT does is to allocate sufficient bits to accomodate any +case. What GNAT does is to allocate sufficient bits to accommodate any possible dynamic values for the bounds at run-time. So far, so good, but GNAT has to obey the RM rules, so the question is diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi index 0f6109e..5f36a47 100644 --- a/gcc/ada/gnat_rm.texi +++ b/gcc/ada/gnat_rm.texi @@ -18572,7 +18572,7 @@ Value_Size Note: the entries marked '*' are not actually specified by the Ada Reference Manual, which has nothing to say about size in the dynamic -case. What GNAT does is to allocate sufficient bits to accomodate any +case. What GNAT does is to allocate sufficient bits to accommodate any possible dynamic values for the bounds at run-time. So far, so good, but GNAT has to obey the RM rules, so the question is diff --git a/gcc/ada/libgnat/s-secsta.ads b/gcc/ada/libgnat/s-secsta.ads index d06e97f..504c891 100644 --- a/gcc/ada/libgnat/s-secsta.ads +++ b/gcc/ada/libgnat/s-secsta.ads @@ -264,7 +264,7 @@ private Memory_Alignment : constant := Standard'Maximum_Alignment * 2; -- The memory alignment we will want to honor on every allocation. -- - -- At this stage, gigi assumes we can accomodate any alignment requirement + -- At this stage, gigi assumes we can accommodate any alignment requirement -- there might be on the data type for which the memory gets allocated (see -- build_call_alloc_dealloc). -- |