Lines Matching full:c99
183 9899:1999, and is commonly known as "C99". GCC has incomplete support
186 standard, use `-std=c99' or `-std=iso9899:1999'. (While in
203 `-std=gnu99' (for C99 with GNU extensions) or `-std=gnu1x' (for C1X
206 future release when the C99 support is complete. Some features that
207 are part of the C99 standard are accepted as extensions in C90 mode.
214 and `<stddef.h>'; since AMD1, also those in `<iso646.h>'; and in C99,
216 types, added in C99, are not required for freestanding implementations.
242 implementations, nor yet all the facilities required by C99 of
1807 `c99'
1811 ISO C99. Note that this standard is not yet fully supported;
1824 GNU dialect of ISO C90 (including some C99 features). This is
1829 GNU dialect of ISO C99. When ISO C99 is fully implemented in
1860 semantics for `inline' functions when in C99 mode. *Note An
1864 in C99 mode. Using this option is roughly equivalent to adding the
1868 The option `-fno-gnu89-inline' explicitly tells GCC to use the C99
1869 semantics for `inline' when in C99 or gnu99 mode (i.e., it
1904 C99 mode (`-std=c99' or `-std=gnu99'), this switch only affects
1906 keyword in ISO C99.
3157 GNU libc version 2.2. These include all ISO C90 and C99 features,
3250 In C99 mode (`-std=c99' or `-std=gnu99'), this warning is enabled
3913 This construct, known from C++, was introduced with ISO C99 and is
4399 GNU alternate syntax when in pedantic ISO C99 mode. This is
4446 in C99, it was raised to 4095. C++98 does not specify a normative
4457 pragma from the decimal floating-point extension to C99.
7283 (undefined behavior according to ISO C99 6.2.7), a non-fatal
7586 will follow the rules specified in ISO C99; in particular, both
7590 such as `-std=c99' is used.
7728 using C99's `FENV_ACCESS' pragma. This command line option will
7758 This option controls the default setting of the ISO C99
9074 `c99'
9217 default for C99 and C++.
16745 against startup code that assumes a C99-style interface to `main',
17465 considered to be a match. For C99 and C++ extended identifiers,
18005 * `How a diagnostic is identified (C90 3.7, C99 3.10, C90 and C99
18012 translation phase 3 (C90 and C99 5.1.1.2).'
18028 the source character set in translation phase 1 (C90 and C99
18042 and their correspondence to universal character names (C99 6.4.2).'
18048 (C90 6.1.2, C90 and C99 5.2.4.1, C99 6.4.2).'
18057 This is a property of the linker. C99 requires that case
18068 * `The number of bits in a byte (C90 3.4, C99 3.6).'
18073 C99 5.2.1).'
18079 and C99 5.2.2).'
18085 (C90 6.1.2.5, C99 6.2.5).'
18091 6.2.1.1, C99 6.2.5, C99 6.3.1.1).'
18099 character set (C90 6.1.3.4, C99 6.4.4.4, C90 and C99 5.1.1.2).'
18106 C99 6.4.4.4).'
18114 (C90 6.1.3.4, C99 6.4.4.4).'
18122 character code (C90 6.1.3.4, C99 6.4.4.4).'
18128 corresponding wide character codes (C90 6.1.4, C99 6.4.5).'
18135 (C90 6.1.4, C99 6.4.5).'
18146 * `Any extended integer types that exist in the implementation (C99
18154 (C99 6.2.6.2).'
18160 integer type with the same precision (C99 6.3.1.1).'
18166 object of that type (C90 6.2.1.2, C99 6.3.1.3).'
18172 6.3, C99 6.5).'
18179 GCC does not use the latitude given in C99 only to treat certain
18184 GCC always follows the C99 requirement that the result of division
18196 floating-point results (C90 and C99 5.2.4.2.2).'
18201 `FLT_ROUNDS' (C90 and C99 5.2.4.2.2).'
18206 values of `FLT_EVAL_METHOD' (C99 5.2.4.2.2).'
18212 value (C90 6.2.1.3, C99 6.3.1.4).'
18214 C99 Annex F is followed.
18217 converted to a narrower floating-point number (C90 6.2.1.4, C99
18220 C99 Annex F is followed.
18225 6.1.3.1, C99 6.4.4.2).'
18227 C99 Annex F is followed.
18230 disallowed by the `FP_CONTRACT' pragma (C99 6.5).'
18236 * `The default state for the `FENV_ACCESS' pragma (C99 7.6.1).'
18242 environments, and classifications, and their macro names (C99 7.6,
18243 C99 7.12).'
18248 * `The default state for the `FP_CONTRACT' pragma (C99 7.12.2).'
18256 an IEC 60559 conformant implementation (C99 F.9).'
18263 60559 conformant implementation (C99 F.9).'
18276 (C90 6.3.4, C99 6.3.2.3).'
18293 arithmetic as proscribed in C99 6.5.6/8.
18296 the same array (C90 6.3.6, C99 6.5.6).'
18314 storage-class specifier are effective (C90 6.5.1, C99 6.7.1).'
18334 specifier are effective (C99 6.7.4).'
18357 6.5.2.1, C99 6.7.2, C99 6.7.2.1).'
18363 `unsigned int' (C99 6.7.2.1).'
18368 6.5.2.1, C99 6.7.2.1).'
18373 C99 6.7.2.1).'
18378 6.5.2.1, C99 6.7.2.1).'
18383 6.5.2.2, C99 6.7.2.2).'
18403 volatile-qualified type (C90 6.5.3, C99 6.7.3).'
18473 or external source file names (C90 6.1.7, C99 6.4.7).'
18477 character constant in the execution character set (C90 6.8.1, C99
18482 negative value (C90 6.8.1, C99 6.10.1).'
18486 identified (C90 6.8.2, C99 6.10.2).'
18489 delimited header (C90 6.8.2, C99 6.10.2).'
18493 header name (C90 6.8.2, C99 6.10.2).'
18495 * `The nesting limit for `#include' processing (C90 6.8.2, C99
18500 constant or string literal (C99 6.10.3.2).'
18503 6.8.6, C99 6.10.6).'
18510 the date and time of translation are not available (C90 6.8.8, C99
18524 7.1.6, C99 7.17).'
18538 headers `<float.h>', `<limits.h>', and `<stdint.h>' (C90 and C99
18539 5.2.4.2, C99 7.18.2, C99 7.18.3).'
18544 explicitly specified in this International Standard) (C99
18550 C99 6.5.3.4).'
18638 Some features that are in ISO C99 but not C90 or C++ are also, as
19324 ISO C99 supports data types for integers that are at least 64 bits wide,
19354 ISO C99 supports complex floating data types, and as an extension GCC
19356 types which are not part of ISO C99. You can declare complex types
19371 you have an ISO C99 conforming C library (such as GNU libc), and want
19378 use the ISO C99 functions `crealf', `creal', `creall', `cimagf',
19384 type, you should use the ISO C99 functions `conjf', `conj' and `conjl',
19515 ISO C99 supports floating-point numbers written not only in the usual
19675 In ISO C99, you would use a "flexible array member", which is slightly
19757 Variable-length automatic arrays are allowed in ISO C99, and as an
19818 declaration in parameter name and data type. ISO C99 does not support
19900 In ISO C99, arrays that are not lvalues still decay to pointers, and
19904 mode, though otherwise they do not decay to pointers outside C99 mode.
19938 As in standard C++ and ISO C99, the elements of an aggregate
19955 ISO C99 supports compound literals. A compound literal looks like a
19991 C99, because the initializer is not a constant). It is handled as if
20017 In ISO C99 you can give the elements in any order, specifying the array
20183 ISO C99 and ISO C++ allow declarations and code to be freely mixed
20293 in C99 or gnu99 mode.
20315 Since ISO C99 specifies a different semantics for `inline', this
20662 `stdio.h'. In C99 mode, the functions `snprintf', `vsnprintf',
21975 The ISO C99 standard includes `_Pragma', which now allows pragmas to
22051 C99, so the ambiguity does not arise there.
22122 the `[]' of a parameter array declarator, in the C99 construct by which
22138 Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration `T D1',
22250 specifying a version of ISO C before C99, or `-ansi' (equivalent to
23258 when `-std=c99', `-std=c1x', `-std=gnu99' or `-std=gnu1x' (without
26216 `inline' can be used in a program compiled with `-std=c99' or
26217 `-std=c1x'). The ISO C99 keyword `restrict' is only available when
26218 `-std=gnu99' (which will eventually be the default) or `-std=c99' (or
26267 of the C99 standard:
26777 Outside strict ISO C mode (`-ansi', `-std=c90', `-std=c99' or
26794 The ISO C99 functions `_Exit', `acoshf', `acoshl', `acosh', `asinhf',
26823 There are also built-in versions of the ISO C99 functions `acosf',
26831 purpose to which ISO C99 puts them. All these functions have
26854 GCC provides built-in versions of the ISO C99 floating point comparison
27148 This built-in implements the C99 fpclassify functionality. The
27173 This function is suitable for implementing the ISO C99 macro
27188 This is an implementation of the ISO C99 function `nan'.
27190 Since ISO C99 defines this function in terms of `strtod', which we
38200 * C99 Thread-Local Edits::
38204 File: gcc.info, Node: C99 Thread-Local Edits, Next: C++98 Thread-Local Edits, Up: Thread-Local
38209 The following are a set of changes to ISO/IEC 9899:1999 (aka C99) that
38259 File: gcc.info, Node: C++98 Thread-Local Edits, Prev: C99 Thread-Local Edits, Up: Thread-Local
38407 * Restricted Pointers:: C99 restricted pointers and references.
38478 As with the C front end, G++ understands the C99 feature of restricted
38480 qualifier. Because you cannot compile C++ by specifying the `-std=c99'
39967 * c99-like fast enumeration syntax::
39972 File: gcc.info, Node: Using fast enumeration, Next: c99-like fast enumeration syntax, Up: Fast enumeration
40008 File: gcc.info, Node: c99-like fast enumeration syntax, Next: Fast enumeration details, Prev: Using fast enumeration, Up: Fast enumeration
40010 8.9.2 c99-like fast enumeration syntax
40013 A c99-like declaration syntax is also allowed:
40036 Note that the option `-std=c99' is not required to allow this syntax
40040 File: gcc.info, Node: Fast enumeration details, Next: Fast enumeration protocol, Prev: c99-like fast enumeration syntax, Up: Fast enumeration
41433 includes nearly complete C99 support. You could also ask your
43637 ISO C99 support, CFG dumping support, etc., plus support of the
43960 point numbers wider than 64 bits and for ISO C99 support.
43967 and ISO C99 support, and continuous emphasis on (and contributions
47529 * C99: Standards. (line 13)
47992 * ISO C99: Standards. (line 13)
49019 Node: C99 Thread-Local Edits1582186
49053 Node: c99-like fast enumeration syntax1656506
