Lines Matching full:them
62 how to port them to new targets and some information about how to write
160 you want them to be errors rather than warnings). *Note Options
233 environment, you will need to find them elsewhere (for example, in the
289 documented here, since you rarely need to use any of them.
1238 them will also be displayed.
1270 recognizes files with these names and compiles them as C++ programs
1316 want to use them in an ISO C program, of course, but it is useful
1317 to put them in header files that might be included in compilations
1616 has been added for putting variables into BSS without making them
2222 them.
2273 the remaining front ends would be able to digest them correctly.
2347 these escape routes; application programs should avoid them.
2591 with no sequence point between them, the order in which the
2889 them warn about constructions that users generally do not consider
3017 traditional C by indenting them. Some traditional
3670 `-femit-struct-debug-detailed' does not yet implement them.
4229 that produce them. You can use the `-frandom-seed' option to
4251 them in the current directory and name them based on the source
4300 switches that enable them. The directory name is separated from
4324 components where `gcc' expects to find them, or you can set the
4326 installed them. Don't forget the trailing `/'. *Note Environment
4377 from all of the files when compiling each of them.
4493 the stack for several function calls and pops them all at once.
4499 arithmetic on them. This produces better code by making all memory
4507 doing arithmetic on them.
5178 sections and linker must place them in a reasonable way.
5349 statements. Output them in the same order that they appear in the
5418 modifying them to store all pertinent intermediate computations
5585 actually performs the optimizations based on them. Currently the
5757 on them. This value is ignored in the case where all
5770 compilation process, and unfactors them as late as possible.
6272 by default and have no options to control them.
6346 them.
6354 Some of them are left out by default, since they trigger
6408 and adds them to the dependency list without raising an error.
6434 specify. If you want multiple targets, you can specify them as a
6796 trigraphs, but in standard-conforming modes it converts them. See
7039 supply the correct flags may lead to subtle defects. Supplying them in
7173 3.15 Specifying subprocesses and the switches to pass to them
7300 expanding these sequences. Therefore you can concatenate them together
7301 or combine them with constant text in a single argument.
7380 automatically placed around them. You should write spaces around
7670 them if you can just run that directly.
8476 man page describes them in detail.
8496 built so as not to call them.
9042 floats on 4 byte boundaries. `-malign-300' causes them to be
9545 `bss' or `data' segments. `-msvr3-shlib' places them into `bss'.
10040 generate special code to reference them.
10044 generate special instructions to reference them.
10634 support them and `-mdivide-breaks' to force the use of breaks.
10674 assembler files (with a `.s' suffix) when assembling them.
11136 disable them individually if you're sure it'll work in your
11257 64-bit `long' type, and the infrastructure needed to support them.
12636 them as close as possible to their references. This may be
12686 Most of them have both positive and negative forms; the negative form
12813 section of the object file, rather than generating them as common
12816 error when you link them. The only reason this might be useful is
13139 An overview of these techniques, their benefits and how to use them
13150 operates. Some of them work by specifying directories or prefixes to
13237 for special linker files, if it can't find them using
13356 a project, include them from another header file, precompile that header
13476 of the source file, to make them available for any calls that precede
13516 compilation options to make them a single word in the shell.
14210 These extensions are available in C and Objective-C. Most of them are
14256 (With them you can define ``built-in'' functions.)
14413 contains nested loops, a `goto' can be useful for breaking out of them.
14584 technique called "trampolines". A paper describing them is available as
14651 therefore, not recommended to use them outside very simple functions
14815 and as an extension GCC supports them in C89 mode and in C++. Simply
14845 supports them in C89 mode and in C++, and supports complex integer data
14995 elements in array" is given, and the excess elements (all of them, in
15055 extension GCC accepts them in C89 mode and in C++. (However, GCC's
15147 GNU CPP has two further variadic macro extensions, and permits them to
15201 them. As an extension, GCC allows such arrays to be subscripted in C89
15410 Currently, GCC will discard them and issue a warning.
15518 keyword. This allows you to use them in header files without being
16035 their own functions that never return. You can declare them
16394 translation units and performing a reloadable link on them.
16405 You can specify multiple attributes in a declaration by separating them
16718 machines, typically because the target assembler does not allow them.
16776 keyword. This allows you to use them in header files without being
17074 may be that the Microsoft ABI packs them differently than GCC
17075 would normally pack them. Particularly when moving packed data
17519 may be that the Microsoft ABI packs them differently than GCC
17520 would normally pack them. Particularly when moving packed data
17528 To specify multiple attributes, separate them by commas within the
17737 The connection between them is expressed by constraints which say they
17897 they cannot take account of them when deciding how to optimize.
17900 encapsulate them in macros that look like functions. For example,
17922 used, but you must be careful, because the compiler may eliminate them
17923 if the output operands aren't used, or move them out of loops, or
18076 and replaces them with one output. The user must code the `st(1)'
18233 them an input-output operand:
19788 (unless you recompile them specially for the task at hand).
19819 variables, and to restore them in a `longjmp'. This way, the same
19913 as macros to replace them with the customary keywords. It looks like
20009 3.4 and later treat them as variables, like `__func__'. In C++,
20131 You can declare variables and use them in function calls and returns,
20297 them, it returns `(size_t) -1' for TYPE 0 or 1 and `(size_t) 0'
20299 and all of them are known at compile time, the returned number is
20390 the compiler is able to optimize them
20467 purpose to which ISO C99 puts them. All these functions have
20659 supports them, data prefetch instructions will be generated. If
21382 of them generate the machine instruction that is part of the name.
21422 of them generate the machine instruction that is part of the name.
21440 All of them generate the machine instruction that is part of the name.
21544 All of them generate the machine instruction that is part of the name.
21701 All of them generate the machine instruction that is part of the name.
21722 All of them generate the machine instruction that is part of the name.
21746 `-march=athlon' are used. All of them generate the machine instruction
24242 may make them incompatible. This pragma is useful when a
24335 platforms whose system headers need them. To get this effect on all
24451 them as errors depending on which preprocessor macros are defined.
24456 controlled by `-W...') can be controlled, and not all of them.
24458 controllable and which option controls them.
24471 your sources, the only supported location for them is before any
24953 will use them. This way one copy will override all the others, but the
24977 mentioned in *Note Vague Linkage::. Using them can actually cause your
25070 emits template instances in each translation unit that uses them,
25071 and the linker collapses them together. The advantage of this
25146 perhaps putting them in the translation units where the instances
25168 other files) without having to specify them as well.
25314 writing C++ code that uses Java exceptions, and handle them
25334 destructors when exceptions are thrown through them.
25711 the allocated objects, yet allow them to be collected. This kind of
25774 class. To be able to support them, the GNU Objective-C compiler
25804 will find them at runtime).
26047 your complex macros behave like functions, you can replace them with
26171 `gcov' development progresses -- do not rely on them remaining
26373 combining them with other lines. For example, code like this:
26481 use them for profile directed optimizations (`--use-profile'), or to
26491 of these are not GCC bugs per se--if they were, we would fix them. But
26629 may even be impossible to generate them.
26970 way around them.
27022 look for them. The scripts adapt to various systems by searching
27038 them into memory truncates them.
27051 destructor are unused and removing them before the scanning can
27142 declarations for them after declaring the template, but before
27358 without them.
27369 macro calls, you can easily convert them manually.
27375 instances and warn about them.
27380 There is no automatic way to verify that you have got them all,
27414 do not make because we think GCC is better without them.
27433 Such assignments must be very common; warning about them would
27471 in every other context, it is cleanest for them to be the same in
27573 program is to have a delay, so deleting them will not make real
27582 taken to execute them, of course). In case the loop can be proved
27647 but include the text `warning:' to distinguish them from error
27653 warnings are issued only if you ask for them, with one of the `-W'
27662 `-pedantic-errors' says to make them errors instead. This does not
27808 it from them. So when you compare distributors, judge them partly by
27830 contribute little, since someone else would surely do them; difficult
27901 source code. And you must show them these terms so they know their
27984 apply to those sections when you distribute them as separate
28163 to attach them to the start of each source file to most effectively
28281 regarding them.
28398 copies, to give them a chance to provide you with an updated
28516 unmodified, and list them all as Invariant Sections of your
28657 them the project would not have been nearly as successful as it has
