Lines Matching full:iso
71 * C Implementation:: How GCC implements the ISO C specification.
150 published in 1990. This standard was ratified as an ISO standard
151 (ISO/IEC 9899:1990) later in 1990. There were no technical differences
153 were renumbered and became clauses in the ISO standard. This standard,
156 ISO standard, also came with a Rationale document. To select this
163 Errors in the 1990 ISO C standard were corrected in two Technical
175 A new edition of the ISO C standard was published in 1999 as ISO/IEC
182 Errors in the 1999 ISO C standard were corrected in two Technical
198 The ISO C standard defines (in clause 4) two classes of conforming
221 when the names of ISO C functions are used, they have the semantics
1302 In C mode, support all ISO C90 programs. In C++ mode, remove GNU
1303 extensions that conflict with ISO C++.
1306 ISO C90 (when compiling C code), or of standard C++ (when
1310 rarely used ISO trigraph feature. For the C compiler, it disables
1316 want to use them in an ISO C program, of course, but it is useful
1321 The `-ansi' option does not cause non-ISO programs to be rejected
1328 ISO standard doesn't call for; this is to avoid interfering with
1332 semantics defined by ISO C (such as `alloca' and `ffs') are not
1344 ISO C90 (same as `-ansi').
1347 ISO C90 as modified in amendment 1.
1353 ISO C99. Note that this standard is not yet fully supported;
1359 Default, ISO C90 plus GNU extensions (including some C99
1364 ISO C99 plus GNU extensions. When ISO C99 is fully
1369 The 1998 ISO C++ standard plus amendments.
1380 The `-std' options specifying some version of ISO C have the same
1381 effects as `-ansi', except that features that were not in ISO C90
1383 the `inline' keyword in ISO C99) are not disabled.
1436 keyword in ISO C99.
1444 `-std' options for strict ISO C conformance are used because they
1445 do not have an ISO standard meaning.
1504 Support ISO C trigraphs. The `-ansi' option (and `-std' options
1505 for strict ISO C conformance) implies `-trigraphs'.
1624 4.1 always worked that way. However, in ISO C++ a friend function
1691 ANSI/ISO C. These include `ffs', `alloca', `_exit', `index',
1731 endless recursions during template class instantiation. ANSI/ISO
2330 Issue all the warnings demanded by strict ISO C and ISO C++;
2332 programs that do not follow ISO C and ISO C++. For ISO C, follows
2333 the version of the ISO C standard specified by any `-std' option
2336 Valid ISO C and ISO C++ programs should compile properly with or
2338 `-std' option specifying the required version of ISO C). However,
2350 Some users try to use `-pedantic' to check programs for strict ISO
2352 want: it finds some non-ISO practices, but not all--only those for
2353 which ISO C _requires_ a diagnostic, and some others for which
2356 A feature to report any failure to conform to ISO C might be
2363 "base standard", the version of ISO C on which the GNU extended
2411 GNU libc version 2.2. These include all ISO C90 and C99 features,
2626 since the value returned by a function is not an lvalue. ISO C
3002 traditional and ISO C. Also warn about ISO C constructs that have
3008 within string literals, but does not in ISO C.
3043 * The ISO type of an integer constant has a different width or
3049 * Usage of ISO string concatenation is detected.
3068 * Use of ISO C style function definitions. This warning
3070 variadic functions because these ISO C features will appear
3079 This construct, known from C++, was introduced with ISO C99 and is
3080 by default allowed in GCC. It is not supported by ISO C90 and was
3120 Warn about ISO C constructs that are outside of the common subset
3121 of ISO C and ISO C++, e.g. request for implicit conversion from
3265 In ISO C and ISO C++, two identifiers are different if they are
3269 avoid confusion, the ISO 10646 standard sets out some
3277 in the ISO 10646 "C" normalized form, "NFC". NFC is the
3280 Unfortunately, there are some characters which ISO C and ISO C++
3283 portable ISO C or C++ and have all your identifiers in NFC.
3294 Some characters in ISO 10646 have distinct meanings but look
3298 has been placed in a superscript. ISO 10646 defines the "NFKC"
3393 type. According to the 1998 ISO C++ standard, applying `offsetof'
3424 Warn if variadic macros are used in pedantic ISO C90 mode, or the
3425 GNU alternate syntax when in pedantic ISO C99 mode. This is
5431 exact implementation of IEEE or ISO rules/specifications for math
5442 exact implementation of IEEE or ISO rules/specifications for math
5460 exact implementation of IEEE or ISO rules/specifications for math
5471 exact implementation of IEEE or ISO rules/specifications.
5485 exact implementation of IEEE or ISO rules/specifications for math
5542 This option controls the default setting of the ISO C99
6294 traditional and ISO C. Also warn about ISO C constructs that have
6521 The ISO C standard from 1990. `c89' is the customary
6533 The revised ISO C standard, published in December 1999.
6544 The 1998 ISO C++ standard plus amendments.
6789 opposed to ISO C preprocessors.
6793 all starting with `??', that are defined by ISO C to stand for
7402 `_L', where L is an uppercase letter. This is for ISO C.
13115 self-documentation of the code. Note that due to ISO C++
13449 add prototypes to a program, thus converting the program to ISO C in
13482 definitions to the old-style pre-ISO form.
13597 A conforming implementation of ISO C is required to document its choice
13600 numbers from the ISO/IEC 9899:1990 and ISO/IEC 9899:1999 standards.
14204 GNU C provides several language features not found in ISO standard C.
14214 Some features that are in ISO C99 but not C89 or C++ are also, as
14711 If you are writing a header file that must work when included in ISO C
14814 ISO C99 supports data types for integers that are at least 64 bits wide,
14844 ISO C99 supports complex floating data types, and as an extension GCC
14846 types which are not part of ISO C99. You can declare complex types
14861 you have an ISO C99 conforming C library (such as GNU libc), and want
14868 use the ISO C99 functions `crealf', `creal', `creall', `cimagf',
14874 type, you should use the ISO C99 functions `conjf', `conj' and `conjl',
14895 defined in the N1176 draft of ISO/IEC WDTR24732. Support for decimal
14934 ISO C99 supports floating-point numbers written not only in the usual
14969 In ISO C90, you would have to give `contents' a length of 1, which
14972 In ISO C99, you would use a "flexible array member", which is slightly
15054 Variable-length automatic arrays are allowed in ISO C99, and as an
15057 to the ISO C99 standard.) These arrays are declared like any other
15116 declaration in parameter name and data type. ISO C99 does not support
15125 In the ISO C standard of 1999, a macro can be declared to accept a
15144 This is in all ways equivalent to the ISO C example above, but arguably
15152 this invocation is invalid in ISO C, because there is no comma after
15198 In ISO C99, arrays that are not lvalues still decay to pointers, and
15236 As in standard C++ and ISO C99, the elements of an aggregate
15253 ISO C99 supports compound literals. A compound literal looks like a
15288 storage duration by compound literals (which is not possible in ISO
15315 In ISO C99 you can give the elements in any order, specifying the array
15481 ISO C99 and ISO C++ allow declarations and code to be freely mixed
15569 Since ISO C99 specifies a different semantics for `inline', this
15860 this manner except when strict ISO C support is requested by
16409 Some people object to the `__attribute__' feature, suggesting that ISO
16422 The ISO C99 standard includes `_Pragma', which now allows pragmas to
16591 are familiar with the formal specification of declarators in the ISO C
16598 does not include an attribute specifier is as in the ISO C standard.
16648 GNU C extends ISO C to allow a function prototype to override a later
16669 Suppose the type `uid_t' happens to be `short'. ISO C does not allow
16675 This restriction of ISO C makes it hard to write code that is portable
16706 specifying a version of ISO C before C99, or `-ansi' (equivalent to
17262 required by the ISO C standard to be at least a perfect multiple of
17571 Inline functions are included in the ISO C99 standard, but there are
17573 the ISO C99 standard requires. GCC will fully support C99 inline
17591 (If you are writing a header file to be included in ISO C programs,
17645 Since GCC 4.3 will implement ISO C99 semantics for inline functions,
17981 If you are writing a header file that should be includable in ISO C
19900 including ISO C programs. The keywords `asm', `typeof' and `inline'
19902 `inline' can be used in a program compiled with `-std=c99'). The ISO
20416 Outside strict ISO C mode (`-ansi', `-std=c89' or `-std=c99'), the
20430 The ISO C99 functions `_Exit', `acoshf', `acoshl', `acosh', `asinhf',
20457 functions except in strict ISO C90 mode (`-ansi' or `-std=c89').
20459 There are also built-in versions of the ISO C99 functions `acosf',
20466 recognized in any mode since ISO C90 reserves these names for the
20467 purpose to which ISO C99 puts them. All these functions have
20470 The ISO C94 functions `iswalnum', `iswalpha', `iswcntrl', `iswdigit',
20473 except in strict ISO C90 mode (`-ansi' or `-std=c89').
20475 The ISO C90 functions `abort', `abs', `acos', `asin', `atan2', `atan',
20490 GCC provides built-in versions of the ISO C99 floating point comparison
20696 implementing the ISO C macro `HUGE_VAL'.
20721 This function is suitable for implementing the ISO C99 macro
20729 This is an implementation of the ISO C99 function `nan'.
20731 Since ISO C99 defines this function in terms of `strtod', which we
24584 must be a CONSTANT-EXPRESSION, as defined in 5.19.2 of the ANSI/ISO C++
24600 5.52.1 ISO/IEC 9899:1999 Edits for Thread-Local Storage
24603 The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that
24655 5.52.2 ISO/IEC 14882:1998 Edits for Thread-Local Storage
24658 The following are a set of changes to ISO/IEC 14882:1998 (aka C++98)
25170 G++ has extended the template instantiation syntax given in the ISO
25415 Now that there is a definitive ISO standard C++, G++ has a specification
26508 compliant with the ISO C standard.
26714 (non-ISO) versions of C.
26736 (following the ISO C rules) its data type is `unsigned long int'.
26782 ISO C does not permit such a construct.
26801 In ISO C, this is not allowed: `long' and other type modifiers
26820 operators such as `+='. GCC, following the ISO standard, does not
26839 declared it to return. But in systems with ISO C headers, `time'
26844 headers (`<time.h>' on systems with ISO C headers) and not to
26885 obvious that what is meant is an operator and two values, the ISO
26907 incompatible with ISO C, and some depend on special features of other
26957 ISO C, POSIX, BSD, SystemV and X/Open compatibility for GNU/Linux and
27004 This behavior may seem silly, but it's what the ISO standard
27007 It's not worth being incompatible with ISO C just to avoid an
27064 definition (the ISO C++ standard) was only recently completed. As a
27095 the ISO standard, you must supply an initializer in one (and only one)
27349 string. ISO C does not require declaring the argument types of
27460 The ISO C standard leaves it up to the implementation whether a
27520 it is safe to use certain features of ISO C, such as function
27521 prototypes or ISO token concatenation. Since plain `gcc' supports
27522 all the features of ISO C, the correct answer to these questions is
27527 an ISO C program, because the ISO C standard says that a conforming
27532 an ISO C library.
27535 does not completely conform to the ISO C standard somehow violates
27537 compilers that claim to support ISO C, such as `gcc -ansi'--not
27538 for other compilers such as plain `gcc'. Whatever the ISO C
27544 option for strict conformance to some version of ISO C. On some
27557 they should concatenate tokens in the ISO C fashion or in the
27564 in ISO C but not in traditional C. Many of these header files can
27620 Some ISO C testsuites report failure when the compiler does not
27623 ISO C requires a "diagnostic" message for certain kinds of invalid
27626 correct ISO C support. If testsuites call this "failure", they
27663 mean that _all_ non-ISO constructs get warnings or errors.
28822 ISO C99 support, CFG dumping support, etc., plus support of the
29106 analysis improvements, ISO C `restrict' support, and serving as
29131 point numbers wider than 64 bits and for ISO C99 support.
29138 and ISO C99 support, and continuous emphasis on (and contributions
29281 ISO).
32432 * ISO 9899: Standards. (line 6)
32433 * ISO C: Standards. (line 6)
32434 * ISO C standard: Standards. (line 6)
32435 * ISO C90: Standards. (line 6)
32436 * ISO C94: Standards. (line 6)
32437 * ISO C95: Standards. (line 6)
32438 * ISO C99: Standards. (line 6)
32439 * ISO C9X: Standards. (line 6)
32440 * ISO support: C Dialect Options. (line 10)
32441 * ISO/IEC 9899: Standards. (line 6)
