Lines Matching full:iso
1362 This turns off certain features of \s-1GCC\s0 that are incompatible with \s-1ISO\s0
1367 rarely used \s-1ISO\s0 trigraph feature. For the C compiler,
1373 \&\fB\-ansi\fR. You would not want to use them in an \s-1ISO\s0 C program, of
1379 The \fB\-ansi\fR option does not cause non-ISO programs to be
1386 \&\s-1ISO\s0 standard doesn't call for; this is to avoid interfering with any
1390 defined by \s-1ISO\s0 C (such as \f(CW\*(C`alloca\*(C'\fR and \f(CW\*(C`ffs\*(C'\fR) are not built-in
1403 incompatible with \s-1ISO\s0 C90, such as the \f(CW\*(C`asm\*(C'\fR and \f(CW\*(C`typeof\*(C'\fR
1405 \&\s-1ISO\s0 C90, such as omitting the middle term of a \f(CW\*(C`?:\*(C'\fR
1423 Support all \s-1ISO\s0 C90 programs (certain \s-1GNU\s0 extensions that conflict
1424 with \s-1ISO\s0 C90 are disabled). Same as \fB\-ansi\fR for C code.
1427 \&\s-1ISO\s0 C90 as modified in amendment 1.
1438 \&\s-1ISO\s0 C99. Note that this standard is not yet fully supported; see
1443 \&\s-1GNU\s0 dialect of \s-1ISO\s0 C90 (including some C99 features). This
1451 \&\s-1GNU\s0 dialect of \s-1ISO\s0 C99. When \s-1ISO\s0 C99 is fully implemented in \s-1GCC\s0,
1455 The 1998 \s-1ISO\s0 \*(C+ standard plus amendments. Same as \fB\-ansi\fR for
1463 The working draft of the upcoming \s-1ISO\s0 \*(C+0x standard. This option
1520 \&\f(CW\*(C`inline\*(C'\fR is a standard keyword in \s-1ISO\s0 C99.
1588 Support \s-1ISO\s0 C trigraphs. The \fB\-ansi\fR option (and \fB\-std\fR
1589 options for strict \s-1ISO\s0 C conformance) implies \fB\-trigraphs\fR.
1717 that way. However, in \s-1ISO\s0 \*(C+ a friend function which is not declared
1782 \&\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,
1821 endless recursions during template class instantiation. \s-1ANSI/ISO\s0 \*(C+
2517 Issue all the warnings demanded by strict \s-1ISO\s0 C and \s-1ISO\s0 \*(C+;
2519 programs that do not follow \s-1ISO\s0 C and \s-1ISO\s0 \*(C+. For \s-1ISO\s0 C, follows the
2520 version of the \s-1ISO\s0 C standard specified by any \fB\-std\fR option used.
2522 Valid \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ programs should compile properly with or without
2524 \&\fB\-std\fR option specifying the required version of \s-1ISO\s0 C). However,
2534 Some users try to use \fB\-pedantic\fR to check programs for strict \s-1ISO\s0
2536 it finds some non-ISO practices, but not all\-\-\-only those for which
2537 \&\s-1ISO\s0 C \fIrequires\fR a diagnostic, and some others for which
2540 A feature to report any failure to conform to \s-1ISO\s0 C might be useful in
2547 corresponding \fIbase standard\fR, the version of \s-1ISO\s0 C on which the \s-1GNU\s0
2672 libc version 2.2. These include all \s-1ISO\s0 C90 and C99 features, as well
2775 such as \f(CW\*(C`const\*(C'\fR. For \s-1ISO\s0 C such a type qualifier has no effect,
2778 \&\s-1ISO\s0 C prohibits qualified \f(CW\*(C`void\*(C'\fR return types on function
3203 \&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
3209 but does not in \s-1ISO\s0 C.
3241 The \s-1ISO\s0 type of an integer constant has a different width or
3246 Usage of \s-1ISO\s0 string concatenation is detected.
3264 Use of \s-1ISO\s0 C style function definitions. This warning intentionally is
3266 because these \s-1ISO\s0 C features will appear in your code when using
3284 construct, known from \*(C+, was introduced with \s-1ISO\s0 C99 and is by default
3285 allowed in \s-1GCC\s0. It is not supported by \s-1ISO\s0 C90 and was not supported by
3318 Disables the warnings about non-ISO \f(CW\*(C`printf\*(C'\fR / \f(CW\*(C`scanf\*(C'\fR format
3342 Warn about \s-1ISO\s0 C constructs that are outside of the common subset of
3343 \&\s-1ISO\s0 C and \s-1ISO\s0 \*(C+, e.g. request for implicit conversion from
3347 Warn about \*(C+ constructs whose meaning differs between \s-1ISO\s0 \*(C+ 1998 and
3348 \&\s-1ISO\s0 \*(C+ 200x, e.g., identifiers in \s-1ISO\s0 \*(C+ 1998 that will become keywords
3349 in \s-1ISO\s0 \*(C+ 200x. This warning is enabled by \fB\-Wall\fR.
3546 In \s-1ISO\s0 C and \s-1ISO\s0 \*(C+, two identifiers are different if they are
3550 the \s-1ISO\s0 10646 standard sets out some \fInormalization rules\fR which
3557 not in the \s-1ISO\s0 10646 \*(L"C\*(R" normalized form, \fI\s-1NFC\s0\fR. \s-1NFC\s0 is the
3560 Unfortunately, there are some characters which \s-1ISO\s0 C and \s-1ISO\s0 \*(C+ allow
3563 \&\s-1ISO\s0 C or \*(C+ and have all your identifiers in \s-1NFC\s0.
3573 Some characters in \s-1ISO\s0 10646 have distinct meanings but look identical
3577 placed in a superscript. \s-1ISO\s0 10646 defines the \fI\s-1NFKC\s0\fR
3691 type. According to the 1998 \s-1ISO\s0 \*(C+ standard, applying \fBoffsetof\fR
3722 Warn if variadic macros are used in pedantic \s-1ISO\s0 C90 mode, or the \s-1GNU\s0
3723 alternate syntax when in pedantic \s-1ISO\s0 C99 mode. This is default.
6244 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
6256 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
6275 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
6285 This violates the \s-1ISO\s0 C and \*(C+ language standard by possibly changing
6312 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
6336 an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications for
6386 This option controls the default setting of the \s-1ISO\s0 C99
7372 \&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C
7620 The \s-1ISO\s0 C standard from 1990. \fBc89\fR is the customary shorthand for
7642 The revised \s-1ISO\s0 C standard, published in December 1999. Before
7660 The 1998 \s-1ISO\s0 \*(C+ standard plus amendments.
7937 opposed to \s-1ISO\s0 C preprocessors.
7942 are defined by \s-1ISO\s0 C to stand for single characters. For example,
14943 On the other hand, this behavior is not required by \s-1ISO\s0 C, and on some
15294 Note that due to \s-1ISO\s0 \*(C+ specification requirements, operator new and
