From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
C++03 has no explicit conversion operators, -and hence using them cannot avoid suprises. +and hence using them cannot avoid surprises. Wait for C++11.
diff --git a/htdocs/contribute.html b/htdocs/contribute.html index e8137edc..7d85d885 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -300,7 +300,7 @@ followed by a colon. For example,Some large components may be subdivided into sub-components. If -the subcomponent name is not disctinct in its own right, you can use the +the subcomponent name is not distinct in its own right, you can use the form component/sub-component:.
[PRnnnnn, PRmmmmm]
. For multiple
bugs, just cite the most relevant one in the summary and use an
-elipsis instead of the second, or subsequent PR numbers; list all the
+ellipsis instead of the second, or subsequent PR numbers; list all the
related PRs in the body of the commit message in the normal way.
It is not necessary to cite bugs that are closed as duplicates of @@ -355,7 +355,7 @@ together.
If you submit a new version of a patch series, then you should start a new email thread (don't reply to the original patch series). This avoids email threads becoming confused between discussions of the -first and subsequent revisions of the patch set. Your cover leter +first and subsequent revisions of the patch set. Your cover letter (0/nnn) should explain clearly what has been changed between the two patch series. Also state if some of the patches are unchanged between revisions; this saves maintainers having to re-review the diff --git a/htdocs/gccmission.html b/htdocs/gccmission.html index 58a12755..1124fe9f 100644 --- a/htdocs/gccmission.html +++ b/htdocs/gccmission.html @@ -55,7 +55,7 @@ GCC.
The current loop optimizer uses information passed by the front end to discover loop constructs to simplify flow analysis. -It is difficult to keep the information up-to-date and nowday +It is difficult to keep the information up-to-date and nowadays it is easy to implement the loop discovery code on CFG.
diff --git a/htdocs/projects/cli.html b/htdocs/projects/cli.html index 47ddb362..4f0baa0b 100644 --- a/htdocs/projects/cli.html +++ b/htdocs/projects/cli.html @@ -152,7 +152,7 @@ front end and the CLI binutils (both Mono based and DotGnu based) .-Unlike a typical GCC back end, the CLI backnend stops the compilation flow +Unlike a typical GCC back end, the CLI backend stops the compilation flow at the end of the middle-end passes and, without going through any RTL pass, it emits CIL bytecode from GIMPLE representation. As a matter of fact, RTL is not a convenient representation to emit diff --git a/htdocs/projects/cxx-reflection/index.html b/htdocs/projects/cxx-reflection/index.html index 2aefd708..709e012f 100644 --- a/htdocs/projects/cxx-reflection/index.html +++ b/htdocs/projects/cxx-reflection/index.html @@ -53,7 +53,7 @@ complete, you should:
Patches that break default bootstraps will be removed (if a fix is not immediately obvious).
-When submitting patches that implement new fonctionalities, please +
When submitting patches that implement new functionalities, please
include a reference to the paper and/or book where you are getting the
complete syntactic and semantic specifications from. If it's your own
research work, include a Technical Report, Thesis or Paper reference
diff --git a/htdocs/projects/optimize.html b/htdocs/projects/optimize.html
index 26262637..6354c726 100644
--- a/htdocs/projects/optimize.html
+++ b/htdocs/projects/optimize.html
@@ -220,7 +220,7 @@ implemented by processor specific instructions. These transformations
are better performed in GCC, both to reduce the overhead of macro
expansion and to take advantage of the functions attributes, for
example to avoid a second call to a pure function altogether. The
-use of these macros tend to cause huge blowup in the size of preprocessed
+use of these macros tend to cause huge increase in the size of preprocessed
source if nested; for example, each nested call to strcpy
expands the source 20-fold, with four nested calls having an expansion
ten megabytes in size. GCC then consumes a huge amount of memory
@@ -290,8 +290,8 @@ target.
Note: If an issue listed in a target specific issues -page, but it clearly is a target indepentent issue, please move it to -a page discussing target indepentent issues
+page, but it clearly is a target independent issue, please move it to +a page discussing target independent issues