summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJan Korous <jkorous@apple.com>2017-10-09 23:45:20 +0000
committerJan Korous <jkorous@apple.com>2017-10-09 23:45:20 +0000
commit0e171eab3e591b413fc98a9d9e21fc003b770200 (patch)
tree7b4fd6f22f7a8f2bd9bb0347bbbd394470742881
parentb87720b77aee65e30a6181e239cbf708f4d29259 (diff)
downloadbcm5719-llvm-0e171eab3e591b413fc98a9d9e21fc003b770200.tar.gz
bcm5719-llvm-0e171eab3e591b413fc98a9d9e21fc003b770200.zip
Fix typos in documentation
Differential Revision: https://reviews.llvm.org/D38711 llvm-svn: 315252
-rw-r--r--clang/docs/InternalsManual.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/clang/docs/InternalsManual.rst b/clang/docs/InternalsManual.rst
index 7f6dba24e61..058c63f0afd 100644
--- a/clang/docs/InternalsManual.rst
+++ b/clang/docs/InternalsManual.rst
@@ -1540,7 +1540,7 @@ Implementation Approach
After trying several different approaches, we've finally converged on a design
(Note, at the time of this writing, not all of this has been implemented,
consider this a design goal!). Our basic approach is to define a single
-recursive method evaluation method (``Expr::Evaluate``), which is implemented
+recursive evaluation method (``Expr::Evaluate``), which is implemented
in ``AST/ExprConstant.cpp``. Given an expression with "scalar" type (integer,
fp, complex, or pointer) this method returns the following information:
@@ -2037,7 +2037,7 @@ are similar.
* ``CodeGenFunction`` contains functions ``ConvertType`` and
``ConvertTypeForMem`` that convert Clang's types (``clang::Type*`` or
``clang::QualType``) to LLVM types. Use the former for values, and the
- later for memory locations: test with the C++ "``bool``" type to check
+ latter for memory locations: test with the C++ "``bool``" type to check
this. If you find that you are having to use LLVM bitcasts to make the
subexpressions of your expression have the type that your expression
expects, STOP! Go fix semantic analysis and the AST so that you don't
OpenPOWER on IntegriCloud