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
1498 ISO C90 (when compiling C code), or of standard C++ (when
1502 rarely used ISO trigraph feature. For the C compiler, it disables
1508 want to use them in an ISO C program, of course, but it is useful
1513 The `-ansi' option does not cause non-ISO programs to be rejected
1520 ISO standard doesn't call for; this is to avoid interfering with
1524 defined by ISO C (such as `alloca' and `ffs') are not built-in
1540 turns off certain features of GCC that are incompatible with ISO
1542 extensions that do not have a meaning in ISO C90, such as omitting
1556 Support all ISO C90 programs (certain GNU extensions that
1557 conflict with ISO C90 are disabled). Same as `-ansi' for C
1561 ISO C90 as modified in amendment 1.
1567 ISO C99. Note that this standard is not yet fully supported;
1573 GNU dialect of ISO C90 (including some C99 features). This is
1578 GNU dialect of ISO C99. When ISO C99 is fully implemented in
1583 The 1998 ISO C++ standard plus amendments. Same as `-ansi' for
1591 The working draft of the upcoming ISO C++0x standard. This
1649 keyword in ISO C99.
1657 `-std' options for strict ISO C conformance are used because they
1658 do not have an ISO standard meaning.
1719 Support ISO C trigraphs. The `-ansi' option (and `-std' options
1720 for strict ISO C conformance) implies `-trigraphs'.
1844 4.1 always worked that way. However, in ISO C++ a friend function
1911 ANSI/ISO C. These include `ffs', `alloca', `_exit', `index',
1951 endless recursions during template class instantiation. ANSI/ISO
2618 Issue all the warnings demanded by strict ISO C and ISO C++;
2620 programs that do not follow ISO C and ISO C++. For ISO C, follows
2621 the version of the ISO C standard specified by any `-std' option
2624 Valid ISO C and ISO C++ programs should compile properly with or
2626 `-std' option specifying the required version of ISO C). However,
2638 Some users try to use `-pedantic' to check programs for strict ISO
2640 want: it finds some non-ISO practices, but not all--only those for
2641 which ISO C _requires_ a diagnostic, and some others for which
2644 A feature to report any failure to conform to ISO C might be
2651 "base standard", the version of ISO C on which the GNU extended
2778 GNU libc version 2.2. These include all ISO C90 and C99 features,
2878 `const'. For ISO C such a type qualifier has no effect, since the
2880 warning is only emitted for scalar types or `void'. ISO C
3294 traditional and ISO C. Also warn about ISO C constructs that have
3300 within string literals, but does not in ISO C.
3335 * The ISO type of an integer constant has a different width or
3341 * Usage of ISO string concatenation is detected.
3360 * Use of ISO C style function definitions. This warning
3362 variadic functions because these ISO C features will appear
3379 This construct, known from C++, was introduced with ISO C99 and is
3380 by default allowed in GCC. It is not supported by ISO C90 and was
3424 Warn about ISO C constructs that are outside of the common subset
3425 of ISO C and ISO C++, e.g. request for implicit conversion from
3429 Warn about C++ constructs whose meaning differs between ISO C++
3430 1998 and ISO C++ 200x, e.g., identifiers in ISO C++ 1998 that will
3431 become keywords in ISO C++ 200x. This warning is enabled by
3618 In ISO C and ISO C++, two identifiers are different if they are
3622 avoid confusion, the ISO 10646 standard sets out some
3630 in the ISO 10646 "C" normalized form, "NFC". NFC is the
3633 Unfortunately, there are some characters which ISO C and ISO C++
3636 portable ISO C or C++ and have all your identifiers in NFC.
3647 Some characters in ISO 10646 have distinct meanings but look
3651 has been placed in a superscript. ISO 10646 defines the "NFKC"
3746 type. According to the 1998 ISO C++ standard, applying `offsetof'
3777 Warn if variadic macros are used in pedantic ISO C90 mode, or the
3778 GNU alternate syntax when in pedantic ISO C99 mode. This is
5909 implementation of IEEE or ISO rules/specifications for math
5921 implementation of IEEE or ISO rules/specifications for math
5940 implementation of IEEE or ISO rules/specifications for math
5950 operations. This violates the ISO C and C++ language standard by
5978 implementation of IEEE or ISO rules/specifications for math
6004 exact implementation of IEEE or ISO rules/specifications for math
6060 This option controls the default setting of the ISO C99
6937 traditional and ISO C. Also warn about ISO C constructs that have
7166 The ISO C standard from 1990. `c89' is the customary
7178 The revised ISO C standard, published in December 1999.
7189 The 1998 ISO C++ standard plus amendments.
7449 opposed to ISO C preprocessors.
7453 all starting with `??', that are defined by ISO C to stand for
8062 `_L', where L is an uppercase letter. This is for ISO C.
14346 self-documentation of the code. Note that due to ISO C++
14683 add prototypes to a program, thus converting the program to ISO C in
14716 definitions to the old-style pre-ISO form.
14831 A conforming implementation of ISO C is required to document its choice
14834 numbers from the ISO/IEC 9899:1990 and ISO/IEC 9899:1999 standards.
15438 GNU C provides several language features not found in ISO standard C.
15448 Some features that are in ISO C99 but not C89 or C++ are also, as
16009 If you are writing a header file that must work when included in ISO C
16112 ISO C99 supports data types for integers that are at least 64 bits wide,
16142 ISO C99 supports complex floating data types, and as an extension GCC
16144 types which are not part of ISO C99. You can declare complex types
16159 you have an ISO C99 conforming C library (such as GNU libc), and want
16166 use the ISO C99 functions `crealf', `creal', `creall', `cimagf',
16172 type, you should use the ISO C99 functions `conjf', `conj' and `conjl',
16216 defined in the N1176 draft of ISO/IEC WDTR24732. Support for decimal
16252 ISO C99 supports floating-point numbers written not only in the usual
16275 defined in the N1169 draft of ISO/IEC DTR 18037. Support for
16346 In ISO C90, you would have to give `contents' a length of 1, which
16349 In ISO C99, you would use a "flexible array member", which is slightly
16431 Variable-length automatic arrays are allowed in ISO C99, and as an
16434 to the ISO C99 standard.) These arrays are declared like any other
16493 declaration in parameter name and data type. ISO C99 does not support
16502 In the ISO C standard of 1999, a macro can be declared to accept a
16521 This is in all ways equivalent to the ISO C example above, but arguably
16529 this invocation is invalid in ISO C, because there is no comma after
16575 In ISO C99, arrays that are not lvalues still decay to pointers, and
16613 As in standard C++ and ISO C99, the elements of an aggregate
16630 ISO C99 supports compound literals. A compound literal looks like a
16665 storage duration by compound literals (which is not possible in ISO
16692 In ISO C99 you can give the elements in any order, specifying the array
16858 ISO C99 and ISO C++ allow declarations and code to be freely mixed
16988 Since ISO C99 specifies a different semantics for `inline', this
17325 this manner except when strict ISO C support is requested by
17987 Some people object to the `__attribute__' feature, suggesting that ISO
18000 The ISO C99 standard includes `_Pragma', which now allows pragmas to
18158 are familiar with the formal specification of declarators in the ISO C
18165 does not include an attribute specifier is as in the ISO C standard.
18215 GNU C extends ISO C to allow a function prototype to override a later
18236 Suppose the type `uid_t' happens to be `short'. ISO C does not allow
18242 This restriction of ISO C makes it hard to write code that is portable
18273 specifying a version of ISO C before C99, or `-ansi' (equivalent to
18871 required by the ISO C standard to be at least a perfect multiple of
19204 If you are writing a header file to be included in ISO C89 programs,
19242 As required by ISO C++, GCC considers member functions defined within
19598 If you are writing a header file that should be includable in ISO C
21685 including ISO C programs. The keywords `asm', `typeof' and `inline'
21687 `inline' can be used in a program compiled with `-std=c99'). The ISO
22201 Outside strict ISO C mode (`-ansi', `-std=c89' or `-std=c99'), the
22217 The ISO C99 functions `_Exit', `acoshf', `acoshl', `acosh', `asinhf',
22244 functions except in strict ISO C90 mode (`-ansi' or `-std=c89').
22246 There are also built-in versions of the ISO C99 functions `acosf',
22253 recognized in any mode since ISO C90 reserves these names for the
22254 purpose to which ISO C99 puts them. All these functions have
22257 The ISO C94 functions `iswalnum', `iswalpha', `iswcntrl', `iswdigit',
22260 except in strict ISO C90 mode (`-ansi' or `-std=c89').
22262 The ISO C90 functions `abort', `abs', `acos', `asin', `atan2', `atan',
22277 GCC provides built-in versions of the ISO C99 floating point comparison
22504 implementing the ISO C macro `HUGE_VAL'.
22529 This function is suitable for implementing the ISO C99 macro
22537 This is an implementation of the ISO C99 function `nan'.
22539 Since ISO C99 defines this function in terms of `strtod', which we
32703 must be a CONSTANT-EXPRESSION, as defined in 5.19.2 of the ANSI/ISO C++
32719 5.54.1 ISO/IEC 9899:1999 Edits for Thread-Local Storage
32722 The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that
32774 5.54.2 ISO/IEC 14882:1998 Edits for Thread-Local Storage
32777 The following are a set of changes to ISO/IEC 14882:1998 (aka C++98)
33312 G++ has extended the template instantiation syntax given in the ISO
33675 Now that there is a definitive ISO standard C++, G++ has a specification
34768 compliant with the ISO C standard.
34965 (non-ISO) versions of C.
34987 (following the ISO C rules) its data type is `unsigned long int'.
35033 ISO C does not permit such a construct.
35052 In ISO C, this is not allowed: `long' and other type modifiers
35071 operators such as `+='. GCC, following the ISO standard, does not
35090 declared it to return. But in systems with ISO C headers, `time'
35095 headers (`<time.h>' on systems with ISO C headers) and not to
35136 obvious that what is meant is an operator and two values, the ISO
35158 incompatible with ISO C, and some depend on special features of other
35208 ISO C, POSIX, BSD, SystemV and X/Open compatibility for GNU/Linux and
35255 This behavior may seem silly, but it's what the ISO standard
35258 It's not worth being incompatible with ISO C just to avoid an
35315 definition (the ISO C++ standard) was only recently completed. As a
35346 the ISO standard, you must supply an initializer in one (and only one)
35600 string. ISO C does not require declaring the argument types of
35711 The ISO C standard leaves it up to the implementation whether a
35771 it is safe to use certain features of ISO C, such as function
35772 prototypes or ISO token concatenation. Since plain `gcc' supports
35773 all the features of ISO C, the correct answer to these questions is
35778 an ISO C program, because the ISO C standard says that a conforming
35783 an ISO C library.
35786 does not completely conform to the ISO C standard somehow violates
35788 compilers that claim to support ISO C, such as `gcc -ansi'--not
35789 for other compilers such as plain `gcc'. Whatever the ISO C
35795 option for strict conformance to some version of ISO C. On some
35808 they should concatenate tokens in the ISO C fashion or in the
35815 in ISO C but not in traditional C. Many of these header files can
35871 Some ISO C testsuites report failure when the compiler does not
35874 ISO C requires a "diagnostic" message for certain kinds of invalid
35877 correct ISO C support. If testsuites call this "failure", they
35914 mean that _all_ non-ISO constructs get warnings or errors.
37435 ISO C99 support, CFG dumping support, etc., plus support of the
37727 analysis improvements, ISO C `restrict' support, and serving as
37752 point numbers wider than 64 bits and for ISO C99 support.
37759 and ISO C99 support, and continuous emphasis on (and contributions
37902 ISO).
41314 * ISO 9899: Standards. (line 13)
41315 * ISO C: Standards. (line 13)
41316 * ISO C standard: Standards. (line 13)
41317 * ISO C90: Standards. (line 13)
41318 * ISO C94: Standards. (line 13)
41319 * ISO C95: Standards. (line 13)
41320 * ISO C99: Standards. (line 13)
41321 * ISO C9X: Standards. (line 13)
41322 * ISO support: C Dialect Options. (line 10)
41323 * ISO/IEC 9899: Standards. (line 13)
