Lines Matching full:iso
74 * C Implementation:: How GCC implements the ISO C specification.
156 published in 1990. This standard was ratified as an ISO standard
157 (ISO/IEC 9899:1990) later in 1990. There were no technical differences
159 were renumbered and became clauses in the ISO standard. This standard,
162 ISO standard, also came with a Rationale document. To select this
169 Errors in the 1990 ISO C standard were corrected in two Technical
181 A new edition of the ISO C standard was published in 1999 as ISO/IEC
188 Errors in the 1999 ISO C standard were corrected in three Technical
204 The ISO C standard defines (in clause 4) two classes of conforming
227 when the names of ISO C functions are used, they have the semantics
255 GCC supports the ISO C++ standard (1998) and contains experimental
256 support for the upcoming ISO C++ standard (200x).
258 The original ISO C++ standard was published as the ISO standard
259 (ISO/IEC 14882:1998) and amended by a Technical Corrigenda published in
260 2003 (ISO/IEC 14882:2003). These standards are referred to as C++98 and
268 The ISO C++ committee is working on a new ISO C++ standard, dubbed
273 available on the ISO C++ committee's web site at
1563 ISO C90 (when compiling C code), or of standard C++ (when
1567 rarely used ISO trigraph feature. For the C compiler, it disables
1573 want to use them in an ISO C program, of course, but it is useful
1578 The `-ansi' option does not cause non-ISO programs to be rejected
1585 ISO standard doesn't call for; this is to avoid interfering with
1589 defined by ISO C (such as `alloca' and `ffs') are not built-in
1605 turns off certain features of GCC that are incompatible with ISO
1607 extensions that do not have a meaning in ISO C90, such as omitting
1621 Support all ISO C90 programs (certain GNU extensions that
1622 conflict with ISO C90 are disabled). Same as `-ansi' for C
1626 ISO C90 as modified in amendment 1.
1632 ISO C99. Note that this standard is not yet fully supported;
1638 GNU dialect of ISO C90 (including some C99 features). This is
1643 GNU dialect of ISO C99. When ISO C99 is fully implemented in
1648 The 1998 ISO C++ standard plus amendments. Same as `-ansi' for
1656 The working draft of the upcoming ISO C++0x standard. This
1714 keyword in ISO C99.
1722 `-std' options for strict ISO C conformance are used because they
1723 do not have an ISO standard meaning.
1784 Support ISO C trigraphs. The `-ansi' option (and `-std' options
1785 for strict ISO C conformance) implies `-trigraphs'.
1909 4.1 always worked that way. However, in ISO C++ a friend function
1976 ANSI/ISO C. These include `ffs', `alloca', `_exit', `index',
2016 endless recursions during template class instantiation. ANSI/ISO
2693 Issue all the warnings demanded by strict ISO C and ISO C++;
2695 programs that do not follow ISO C and ISO C++. For ISO C, follows
2696 the version of the ISO C standard specified by any `-std' option
2699 Valid ISO C and ISO C++ programs should compile properly with or
2701 `-std' option specifying the required version of ISO C). However,
2713 Some users try to use `-pedantic' to check programs for strict ISO
2715 want: it finds some non-ISO practices, but not all--only those for
2716 which ISO C _requires_ a diagnostic, and some others for which
2719 A feature to report any failure to conform to ISO C might be
2726 "base standard", the version of ISO C on which the GNU extended
2849 GNU libc version 2.2. These include all ISO C90 and C99 features,
2952 `const'. For ISO C such a type qualifier has no effect, since the
2954 warning is only emitted for scalar types or `void'. ISO C
3377 traditional and ISO C. Also warn about ISO C constructs that have
3383 within string literals, but does not in ISO C.
3418 * The ISO type of an integer constant has a different width or
3424 * Usage of ISO string concatenation is detected.
3443 * Use of ISO C style function definitions. This warning
3445 variadic functions because these ISO C features will appear
3462 This construct, known from C++, was introduced with ISO C99 and is
3463 by default allowed in GCC. It is not supported by ISO C90 and was
3498 Disables the warnings about non-ISO `printf' / `scanf' format
3522 Warn about ISO C constructs that are outside of the common subset
3523 of ISO C and ISO C++, e.g. request for implicit conversion from
3527 Warn about C++ constructs whose meaning differs between ISO C++
3528 1998 and ISO C++ 200x, e.g., identifiers in ISO C++ 1998 that will
3529 become keywords in ISO C++ 200x. This warning is enabled by
3725 In ISO C and ISO C++, two identifiers are different if they are
3729 avoid confusion, the ISO 10646 standard sets out some
3737 in the ISO 10646 "C" normalized form, "NFC". NFC is the
3740 Unfortunately, there are some characters which ISO C and ISO C++
3743 portable ISO C or C++ and have all your identifiers in NFC.
3754 Some characters in ISO 10646 have distinct meanings but look
3758 has been placed in a superscript. ISO 10646 defines the "NFKC"
3874 type. According to the 1998 ISO C++ standard, applying `offsetof'
3905 Warn if variadic macros are used in pedantic ISO C90 mode, or the
3906 GNU alternate syntax when in pedantic ISO C99 mode. This is
6347 implementation of IEEE or ISO rules/specifications for math
6359 implementation of IEEE or ISO rules/specifications for math
6378 implementation of IEEE or ISO rules/specifications for math
6388 operations. This violates the ISO C and C++ language standard by
6416 implementation of IEEE or ISO rules/specifications for math
6442 exact implementation of IEEE or ISO rules/specifications for math
6494 This option controls the default setting of the ISO C99
7512 traditional and ISO C. Also warn about ISO C constructs that have
7738 The ISO C standard from 1990. `c89' is the customary
7750 The revised ISO C standard, published in December 1999.
7761 The 1998 ISO C++ standard plus amendments.
8028 opposed to ISO C preprocessors.
8032 all starting with `??', that are defined by ISO C to stand for
8658 `_L', where L is an uppercase letter. This is for ISO C.
15003 targets. On the other hand, this behavior is not required by ISO
15350 self-documentation of the code. Note that due to ISO C++
15687 add prototypes to a program, thus converting the program to ISO C in
15720 definitions to the old-style pre-ISO form.
15835 A conforming implementation of ISO C is required to document its choice
15838 numbers from the ISO/IEC 9899:1990 and ISO/IEC 9899:1999 standards.
16442 GNU C provides several language features not found in ISO standard C.
16452 Some features that are in ISO C99 but not C89 or C++ are also, as
17013 If you are writing a header file that must work when included in ISO C
17116 ISO C99 supports data types for integers that are at least 64 bits wide,
17146 ISO C99 supports complex floating data types, and as an extension GCC
17148 types which are not part of ISO C99. You can declare complex types
17163 you have an ISO C99 conforming C library (such as GNU libc), and want
17170 use the ISO C99 functions `crealf', `creal', `creall', `cimagf',
17176 type, you should use the ISO C99 functions `conjf', `conj' and `conjl',
17220 defined in the N1312 draft of ISO/IEC WDTR24732. Support for decimal
17263 ISO C99 supports floating-point numbers written not only in the usual
17286 defined in the N1169 draft of ISO/IEC DTR 18037. Support for
17390 In ISO C90, you would have to give `contents' a length of 1, which
17393 In ISO C99, you would use a "flexible array member", which is slightly
17475 Variable-length automatic arrays are allowed in ISO C99, and as an
17478 to the ISO C99 standard.) These arrays are declared like any other
17537 declaration in parameter name and data type. ISO C99 does not support
17546 In the ISO C standard of 1999, a macro can be declared to accept a
17565 This is in all ways equivalent to the ISO C example above, but arguably
17573 this invocation is invalid in ISO C, because there is no comma after
17619 In ISO C99, arrays that are not lvalues still decay to pointers, and
17657 As in standard C++ and ISO C99, the elements of an aggregate
17674 ISO C99 supports compound literals. A compound literal looks like a
17709 storage duration by compound literals (which is not possible in ISO
17736 In ISO C99 you can give the elements in any order, specifying the array
17902 ISO C99 and ISO C++ allow declarations and code to be freely mixed
18032 Since ISO C99 specifies a different semantics for `inline', this
18379 this manner except when strict ISO C support is requested by
19258 Some people object to the `__attribute__' feature, suggesting that ISO
19271 The ISO C99 standard includes `_Pragma', which now allows pragmas to
19429 are familiar with the formal specification of declarators in the ISO C
19436 does not include an attribute specifier is as in the ISO C standard.
19486 GNU C extends ISO C to allow a function prototype to override a later
19507 Suppose the type `uid_t' happens to be `short'. ISO C does not allow
19513 This restriction of ISO C makes it hard to write code that is portable
19544 specifying a version of ISO C before C99, or `-ansi' (equivalent to
20154 required by the ISO C standard to be at least a perfect multiple of
20493 If you are writing a header file to be included in ISO C89 programs,
20531 As required by ISO C++, GCC considers member functions defined within
20889 If you are writing a header file that should be includable in ISO C
23002 including ISO C programs. The keywords `asm', `typeof' and `inline'
23004 `inline' can be used in a program compiled with `-std=c99'). The ISO
23527 Outside strict ISO C mode (`-ansi', `-std=c89' or `-std=c99'), the
23543 The ISO C99 functions `_Exit', `acoshf', `acoshl', `acosh', `asinhf',
23570 functions except in strict ISO C90 mode (`-ansi' or `-std=c89').
23572 There are also built-in versions of the ISO C99 functions `acosf',
23579 recognized in any mode since ISO C90 reserves these names for the
23580 purpose to which ISO C99 puts them. All these functions have
23583 The ISO C94 functions `iswalnum', `iswalpha', `iswcntrl', `iswdigit',
23586 except in strict ISO C90 mode (`-ansi' or `-std=c89').
23588 The ISO C90 functions `abort', `abs', `acos', `asin', `atan2', `atan',
23603 GCC provides built-in versions of the ISO C99 floating point comparison
23832 implementing the ISO C macro `HUGE_VAL'.
23868 This function is suitable for implementing the ISO C99 macro
23883 This is an implementation of the ISO C99 function `nan'.
23885 Since ISO C99 defines this function in terms of `strtod', which we
32057 `__pixel', `pixel', `__bool' and `bool'. When compiling ISO C,
34510 must be a CONSTANT-EXPRESSION, as defined in 5.19.2 of the ANSI/ISO C++
34526 5.54.1 ISO/IEC 9899:1999 Edits for Thread-Local Storage
34529 The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that
34581 5.54.2 ISO/IEC 14882:1998 Edits for Thread-Local Storage
34584 The following are a set of changes to ISO/IEC 14882:1998 (aka C++98)
35119 G++ has extended the template instantiation syntax given in the ISO
35482 Now that there is a definitive ISO standard C++, G++ has a specification
36581 compliant with the ISO C standard.
36778 (non-ISO) versions of C.
36800 (following the ISO C rules) its data type is `unsigned long int'.
36846 ISO C does not permit such a construct.
36865 In ISO C, this is not allowed: `long' and other type modifiers
36884 operators such as `+='. GCC, following the ISO standard, does not
36903 declared it to return. But in systems with ISO C headers, `time'
36908 headers (`<time.h>' on systems with ISO C headers) and not to
36949 obvious that what is meant is an operator and two values, the ISO
36971 incompatible with ISO C, and some depend on special features of other
37021 ISO C, POSIX, BSD, SystemV and X/Open compatibility for GNU/Linux and
37068 This behavior may seem silly, but it's what the ISO standard
37071 It's not worth being incompatible with ISO C just to avoid an
37128 definition (the ISO C++ standard) was only recently completed. As a
37159 the ISO standard, you must supply an initializer in one (and only one)
37413 string. ISO C does not require declaring the argument types of
37524 The ISO C standard leaves it up to the implementation whether a
37584 it is safe to use certain features of ISO C, such as function
37585 prototypes or ISO token concatenation. Since plain `gcc' supports
37586 all the features of ISO C, the correct answer to these questions is
37591 an ISO C program, because the ISO C standard says that a conforming
37596 an ISO C library.
37599 does not completely conform to the ISO C standard somehow violates
37601 compilers that claim to support ISO C, such as `gcc -ansi'--not
37602 for other compilers such as plain `gcc'. Whatever the ISO C
37608 option for strict conformance to some version of ISO C. On some
37621 they should concatenate tokens in the ISO C fashion or in the
37628 in ISO C but not in traditional C. Many of these header files can
37684 Some ISO C testsuites report failure when the compiler does not
37687 ISO C requires a "diagnostic" message for certain kinds of invalid
37690 correct ISO C support. If testsuites call this "failure", they
37727 mean that _all_ non-ISO constructs get warnings or errors.
39248 ISO C99 support, CFG dumping support, etc., plus support of the
39540 analysis improvements, ISO C `restrict' support, and serving as
39565 point numbers wider than 64 bits and for ISO C99 support.
39572 and ISO C99 support, and continuous emphasis on (and contributions
39715 ISO).
43245 * ISO 9899: Standards. (line 13)
43246 * ISO C: Standards. (line 13)
43247 * ISO C standard: Standards. (line 13)
43248 * ISO C90: Standards. (line 13)
43249 * ISO C94: Standards. (line 13)
43250 * ISO C95: Standards. (line 13)
43251 * ISO C99: Standards. (line 13)
43252 * ISO C9X: Standards. (line 13)
43253 * ISO support: C Dialect Options. (line 10)
43254 * ISO/IEC 9899: Standards. (line 13)
