Lines Matching full:iso
1102 In C mode, support all \s-1ISO\s0 C90 programs. In \*(C+ mode,
1103 remove \s-1GNU\s0 extensions that conflict with \s-1ISO\s0 \*(C+.
1105 This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO\s0
1110 rarely used \s-1ISO\s0 trigraph feature. For the C compiler,
1116 \&\fB\-ansi\fR. You would not want to use them in an \s-1ISO\s0 C program, of
1122 The \fB\-ansi\fR option does not cause non-ISO programs to be
1129 \&\s-1ISO\s0 standard doesn't call for; this is to avoid interfering with any
1133 defined by \s-1ISO
1147 \&\s-1ISO\s0 C90 (same as \fB\-ansi\fR).
1150 \&\s-1ISO\s0 C90 as modified in amendment 1.
1161 \&\s-1ISO\s0 C99. Note that this standard is not yet fully supported; see
1166 Default, \s-1ISO\s0 C90 plus \s-1GNU\s0 extensions (including some C99 features).
1173 \&\s-1ISO\s0 C99 plus \s-1GNU\s0 extensions. When \s-1ISO\s0 C99 is fully implemented in \s-1GCC\s0,
1177 The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
1190 The \fB\-std\fR options specifying some version of \s-1ISO\s0 C have the same
1191 effects as \fB\-ansi\fR, except that features that were not in \s-1ISO\s0 C90
1193 the \f(CW\*(C`inline\*(C'\fR keyword in \s-1ISO\s0 C99) are not disabled.
1242 \&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO\s0 C99.
1308 Support \s-1ISO\s0 C trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR
1309 options for strict \s-1ISO\s0 C conformance) implies \fB\-trigraphs\fR.
1432 that way. However, in \s-1ISO\s0 \*(C+ a friend function which is not declared
1497 \&\s-1ANSI/ISO\s0 C. These include \f(CW\*(C`ffs\*(C'\fR, \f(CW\*(C`alloca\*(C'\fR, \f(CW\*(C`_exit\*(C'\fR,
1536 endless recursions during template class instantiation. \s-1ANSI/ISO\s0 \*(C+
2146 Issue all the warnings demanded by strict \s-1ISO\s0 C and \s-1ISO\s0 \*(C+;
2148 programs that do not follow \s-1ISO\s0 C and \s-1ISO\s0 \*(C+. For \s-1ISO\s0 C, follows the
2149 version of the \s-1ISO\s0 C standard specified by any \fB\-std\fR option used.
2151 Valid \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ programs should compile properly with or without
2153 \&\fB\-std\fR option specifying the required version of \s-1ISO\s0 C). However,
2163 Some users try to use \fB\-pedantic\fR to check programs for strict \s-1ISO\s0
2165 it finds some non-ISO practices, but not all\-\-\-only those for which
2166 \&\s-1ISO\s0 C \fIrequires\fR a diagnostic, and some others for which
2169 A feature to report any failure to conform to \s-1ISO\s0 C might be useful in
2176 corresponding \fIbase standard\fR, the version of \s-1ISO\s0 C on which the \s-1GNU\s0
2224 libc version 2.2. These include all \s-1ISO\s0 C90 and C99 features, as well
2446 value returned by a function is not an lvalue. \s-1ISO\s0 C prohibits
2800 \&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
2806 but does not in \s-1ISO\s0 C.
2838 The \s-1ISO\s0 type of an integer constant has a different width or
2843 Usage of \s-1ISO\s0 string concatenation is detected.
2861 Use of \s-1ISO\s0 C style function definitions. This warning intentionally is
2863 because these \s-1ISO\s0 C features will appear in your code when using
2874 ISO\s0 C99 and is by default
2875 allowed in \s-1GCC\s0. It is not supported by \s-1ISO\s0 C90 and was not supported by
2908 Warn about \s-1ISO\s0 C constructs that are outside of the common subset of
2909 \&\s-1ISO\s0 C and \s-1ISO\s0 \*(C+, e.g. request for implicit conversion from
3054 In \s-1ISO\s0 C and \s-1ISO\s0 \*(C+, two identifiers are different if they are
3058 the \s-1ISO\s0 10646 standard sets out some \fInormalization rules\fR which
3065 not in the \s-1ISO\s0 10646 \*(L"C\*(R" normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the
3068 Unfortunately, there are some characters which \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ allow
3071 \&\s-1ISO\s0 C or \*(C+ and have all your identifiers in \s-1NFC\s0.
3081 Some characters in \s-1ISO\s0 10646 have distinct meanings but look identical
3085 placed in a superscript. \s-1ISO\s0 10646 defines the \fI\s-1NFKC\s0\fR
3177 type. According to the 1998 \s-1ISO\s0 \*(C+ standard, applying \fBoffsetof\fR
3208 Warn if variadic macros are used in pedantic \s-1ISO\s0 C90 mode, or the \s-1GNU\s0
3209 alternate syntax when in pedantic \s-1ISO\s0 C99 mode. This is default.
5241 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
5252 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
5270 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
5281 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications.
5294 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
5352 This option controls the default setting of the \s-1ISO\s0 C99
6086 \&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
6335 The \s-1ISO\s0 C standard from 1990. \fBc89\fR is the customary shorthand for
6357 The revised \s-1ISO\s0 C standard, published in December 1999. Before
6375 The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
6615 opposed to \s-1ISO\s0 C preprocessors.
6620 are defined by \s-1ISO\s0 C to stand for single characters. For example,
12868 Note that due to \s-1ISO\s0 \*(C+ specification requirements, operator new and
