diff options
Diffstat (limited to 'string')
| -rw-r--r-- | string/bits/string2.h | 8 | ||||
| -rw-r--r-- | string/string.h | 10 |
2 files changed, 9 insertions, 9 deletions
diff --git a/string/bits/string2.h b/string/bits/string2.h index f0172bf186..8779e35817 100644 --- a/string/bits/string2.h +++ b/string/bits/string2.h @@ -25,11 +25,11 @@ #ifndef __NO_STRING_INLINES /* Unlike the definitions in the header <bits/string.h> the - definitions contained here are not optimizing down to assembler - level. These optimizations are not always a good idea since this + definitions contained here are not optimized down to assembler + level. Those optimizations are not always a good idea since this means the code size increases a lot. Instead the definitions here - optimize some functions in a way which does not dramatically - increase the code size and which does not use assembler. The main + optimize some functions in a way which do not dramatically + increase the code size and which do not use assembler. The main trick is to use GNU CC's `__builtin_constant_p' function. Every function XXX which has a defined version in diff --git a/string/string.h b/string/string.h index 39d1d61193..2b4d6b9545 100644 --- a/string/string.h +++ b/string/string.h @@ -298,18 +298,18 @@ extern char *basename __P ((__const char *__filename)); /* When using GNU CC we provide some optimized versions of selected functions from this header. There are two kinds of optimizations: - - machine-dependent optmizations, most probably using inline - assembler code; these could be quite expensive since the code - size could increase significantly. + - machine-dependent optimizations, most probably using inline + assembler code; these might be quite expensive since the code + size can increase significantly. These optimizations are not used unless the symbol __USE_STRING_INLINES - is defined before including this header + is defined before including this header. - machine-independent optimizations which do not increase the code size significantly and which optimize mainly situations where one or more arguments are compile-time constants. These optimizations are used always when the compiler is - taught to optimized. + taught to optimize. One can inhibit all optimizations by defining __NO_STRING_INLINES. */ |