Many developers are still using __attribute__((optimize())) in
production code, although it quite broken.
* doc/extend.texi (Common Function Attributes) [optimize]:
Discourage use of the optimize attribute.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 883d9b334ab5..a1359f5579ce 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3021,10 +3021,8 @@ that affect more than one function.
@xref{Function Specific Option Pragmas}, for details about the
@samp{#pragma GCC optimize} pragma.
-This can be used for instance to have frequently-executed functions
-compiled with more aggressive optimization options that produce faster
-and larger code, while other functions can be compiled with less
-aggressive options.
+This attribute should only be used for debugging purposes. It is not
+suitable for production code.
@item pure
@cindex @code{pure} function attribute
--
Markus
