aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2016-03-25 04:00:17 +0000
committerAldy Hernandez <aldyh@gcc.gnu.org>2016-03-25 04:00:17 +0000
commit0e92f1e8036a9ce1501d54d6bb39043d74fc8ab0 (patch)
treee715b16a24bc80edde1763993c45bf405f433c79 /gcc/doc
parent836cf7b2335ab698ebf3683da2985d103f631c21 (diff)
downloadgcc-0e92f1e8036a9ce1501d54d6bb39043d74fc8ab0.zip
gcc-0e92f1e8036a9ce1501d54d6bb39043d74fc8ab0.tar.gz
gcc-0e92f1e8036a9ce1501d54d6bb39043d74fc8ab0.tar.bz2
* doc/extend.texi: Fix typo in documentation to pure attribute.
From-SVN: r234477
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/extend.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 623a5d0..6e27029 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3045,7 +3045,7 @@ int square (int) __attribute__ ((pure));
says that the hypothetical function @code{square} is safe to call
fewer times than the program says.
-Some of common examples of pure functions are @code{strlen} or @code{memcmp}.
+Some common examples of pure functions are @code{strlen} or @code{memcmp}.
Interesting non-pure functions are functions with infinite loops or those
depending on volatile memory or other system resource, that may change between
two consecutive calls (such as @code{feof} in a multithreading environment).