From: Chris Lattner Date: Fri, 10 Apr 2009 05:54:56 +0000 (+0000) Subject: typos X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=28935899c1668337982ecaa0aadf999cc40d9adf;p=clang typos git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@68770 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LanguageExtensions.html b/docs/LanguageExtensions.html index 270d32d696..d298a5622d 100644 --- a/docs/LanguageExtensions.html +++ b/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 analyzer_noreturn attribute allows one to annotate such functions as being interpreted as "no return" 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 noreturn).

Usage: The analyzer_noreturn attribute can be placed in the -sampe places where the noreturn attribute can be placed. It is commonly +same places where the noreturn attribute can be placed. It is commonly placed at the end of function prototypes: