summaryrefslogtreecommitdiffstats
path: root/clang/docs
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-04-10 05:54:56 +0000
committerChris Lattner <sabre@nondot.org>2009-04-10 05:54:56 +0000
commitbb72f7741608f258274cb3e413cdb02205544108 (patch)
treece2710e4df3e3c6a1d59042196dfdbda3674f2ba /clang/docs
parentb36338aa007a4afbaf452d6e13d85a2907edb5e6 (diff)
downloadbcm5719-llvm-bb72f7741608f258274cb3e413cdb02205544108.tar.gz
bcm5719-llvm-bb72f7741608f258274cb3e413cdb02205544108.zip
typos
llvm-svn: 68770
Diffstat (limited to 'clang/docs')
-rw-r--r--clang/docs/LanguageExtensions.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/clang/docs/LanguageExtensions.html b/clang/docs/LanguageExtensions.html
index 270d32d6964..d298a5622df 100644
--- a/clang/docs/LanguageExtensions.html
+++ b/clang/docs/LanguageExtensions.html
@@ -303,11 +303,11 @@ panic functions (i.e., they are only called when an internal program error
occurs) but may actually return so that the program can fail gracefully. The
<tt>analyzer_noreturn</tt> attribute allows one to annotate such functions as
being interpreted as &quot;no return&quot; functions by the analyzer (thus
-pruning bogus paths) but will not effect compilation (as in the case of
+pruning bogus paths) but will not affect compilation (as in the case of
<tt>noreturn</tt>).</p>
<p><b>Usage</b>: The <tt>analyzer_noreturn</tt> attribute can be placed in the
-sampe places where the <tt>noreturn</tt> attribute can be placed. It is commonly
+same places where the <tt>noreturn</tt> attribute can be placed. It is commonly
placed at the end of function prototypes:</p>
<pre>
OpenPOWER on IntegriCloud