>,%jV?lf?>UUUUU?p@.symtab.strtab.shstrtab.text.data.bss.rel.text.__ieee754_exp.rodata.ln2HI.rodata.ln2LO.rodata.halF.rodata.cst8.rodata.cst4.note.GNU-stack4!4'404,  DR(`8mH`z l       "( '0 ,8 1@ 7H =P C IX O]s|e_exp.c.LC1.LC2.LC3.LC4.LC5.LC6.LC8.LC9.LC10.LC11.LC12.LC13.LC14__ieee754_exp_GLOBAL_OFFSET_TABLE___GI_expexp X k x        9 A I Q Y s   e_fmod.os/ 1326310717 500 100 100644 1684 ` ELF4( UWVS8[D$LT$D$l$D$T\$T$T$4L$L$0T$,1d$4D$4 t  D$4=v L$T;T$4;l$0}؁7uD$$L$$) D$$L$$-D$$|$4>|$4uD$0D$(L$(-D$4 D$(L$(D$4-D$(|$$|ց,+D$$ ) H1|$(||$4<+D$( )|$0d$4 |$4d$0H|$0D$0D$$+D$(D$ K);l$0L$ y 4p,+T$0 ul$,T$,݄4H,|$ u);l$0x+l$0 u#l$,D$,݄4pL$(~|$(|& T$,D$( ‰T$ l$D$X+D$( ) # ) HD$, D$,D$$$8[^_].symtab.strtab.shstrtab.text.data.bss.rel.text.__ieee754_fmod.rodata.Zero.note.GNU-stack4!4'404, | EPR``b|  <> /9e_fmod.c__ieee754_fmod_GLOBAL_OFFSET_TABLE___GI_fmodfmod * l e_hypot.os/ 1326310717 500 100 100644 1340 ` ELF4( VSĀ݄$\$xL$|݄$T$pT$t9~݄$ɉЉʉ݄$݄$\$hL$lD$h\$`T$dD$`)=~10_~p~;T$X L$XtT$P T$PUVɁ%%\$HL$LD$H\$@T$DD$@X j4T$8D$8 D$0D$4D$0ʁ.Ɂ%%X\$(L$,D$(\$ T$$D$ v4D$L$D$$LD$T$D$D$L$ D$$XZt!$?t$ $ك[^.symtab.strtab.shstrtab.text.data.bss.rel.text.__ieee754_hypot.note.GNU-stack4!4'404+, 4F__VH  ; +*+5+e_hypot.c__ieee754_hypot__ieee754_sqrt__GI_hypothypote_lgamma_r.os/ 1326310717 500 100 100644 6632 ` ELF0 4(UWVSX[l$tD$lT$(D$,D$8D$(E|$8~ X؋T$(T$< ;6|$8yED$lT$l$t$pt$pY^D$0D$4|$8/CD$lT$ t$$?%jjj݃Ƀ$\$\BD$l$\$XZD$ ztP؋T$@$Y^Dhe maximum number of fields in a variable without direct structure accesses for which structure aliasing will consider trying to track each field. The default is 5 .IP "\fBsalias-max-array-elements\fR" 4 .IX Item "salias-max-array-elements" The maximum number of elements an array can have and its elements still be tracked individually by structure aliasing. The default is 4 .IP "\fBsra-max-structure-size\fR" 4 .IX Item "sra-max-structure-size" The maximum structure size, in bytes, at which the scalar replacement of aggregates (\s-1SRA\s0) optimization will perform block copies. The default value, 0, implies that \s-1GCC\s0 will select the most appropriate size itself. .IP "\fBsra-field-structure-ratio\fR" 4 .IX Item "sra-field-structure-ratio" The threshold ratio (as a percentage) between instantiated fields and the complete structure size. We say that if the ratio of the number of bytes in instantiated fields to the number of bytes in the complete structure exceeds this parameter, then block copies are not used. The default is 75. .IP "\fBstruct-reorg-cold-struct-ratio\fR" 4 .IX Item "struct-reorg-cold-struct-ratio" The threshold ratio (as a percentage) between a structure frequency and the frequency of the hottest structure in the program. This parameter is used by struct-reorg optimization enabled by \fB\-fipa\-struct\-reorg\fR. We say that if the ratio of a structure frequency, calculated by profiling, to the hottest structure frequency in the program is less than this parameter, then structure reorganization is not applied to this structure. The default is 10. .IP "\fBmax-crossjump-edges\fR" 4 .IX Item "max-crossjump-edges" The maximum number of incoming edges to consider for crossjumping. The algorithm used by \fB\-fcrossjumping\fR is O(N^2) in the number of edges incoming to each block. Increasing values mean more aggressive optimization, making the compile time increase with probably small improvement in executable size. .IP "\fBmin-crossjump-insns\fR" 4 .IX Item "min-crossjump-insns" The minimum number of instructions which must be matched at the end of two blocks before crossjumping will be performed on them. This value is ignored in the case where all instructions in the block being crossjumped from are matched. The default value is 5. .IP "\fBmax-grow-copy-bb-insns\fR" 4 .IX Item "max-grow-copy-bb-insns" The maximum code size expansion factor when copying basic blocks instead of jumping. The expansion is relative to a jump instruction. The default value is 8. .IP "\fBmax-goto-duplication-insns\fR" 4 .IX Item "max-goto-duplication-insns" The maximum number of instructions to duplicate to a block that jumps to a computed goto. To avoid O(N^2) behavior in a number of passes, \s-1GCC\s0 factors computed gotos early in the compilation process, and unfactors them as late as possible. Only computed jumps at the end of a basic blocks with no more than max-goto-duplication-insns are unfactored. The default value is 8. .IP "\fBmax-delay-slot-insn-search\fR" 4 .IX Item "max-delay-slot-insn-search" The maximum number of instructions to consider when looking for an instruction to fill a delay slot. If more than this arbitrary number of instructions is searched, the time savings from filling the delay slot will be minimal so stop searching. Increasing values mean more aggressive optimization, making the compile time increase with probably small improvement in executable run time. .IP "\fBmax-delay-slot-live-search\fR" 4 .IX Item "max-delay-slot-live-search" When trying to fill delay slots, the maximum number of instructions to consider when searching for a block with valid live register information. Increasing this arbitrarily chosen value means more aggressive optimization, increasing the compile time. This parameter should be removed when the delay slot code is rewritten to maintain the control-flow graph. .IP "\fBmax-gcse-memory\fR" 4 .IX Item "max-gcse-memory" The approximate maximum amount of memory that will be allocated in order to perform the global common subexpression elimination optimization. If more memory than specified is required, the optimization will not be done. .IP "\fBmax-gcse-passes\fR" 4 .IX Item "max-gcse-passes" The maximum number of passes of \s-1GCSE\s0 to run. The default is 1. .IP "\fBmax-pending-list-length\fR" 4 .IX Item "max-pending-list-length" The maximum number of pending dependencies scheduling will allow before flushing the current state and starting over. Large functions with few branches or calls can create excessively large lists which needlessly consume memory and resources. .IP "\fBmax-inline-insns-single\fR" 4 .IX Item "max-inline-insns-single" Several parameters control the tree inliner used in gcc. This number sets the maximum number of instructions (counted in \s-1GCC\s0's internal representation) in a single function that the tree inliner will consider for inlining. This only affects functions declared inline and methods implemented in a class declaration (\*(C+). The default value is 450. .IP "\fBmax-inline-insns-auto\fR" 4 .IX Item "max-inline-insns-auto" When you use \fB\-finline\-functions\fR (included in \fB\-O3\fR), a lot of functions that would otherwise not be considered for inlining by the compiler will be investigated. To those functions, a different (more restrictive) limit compared to functions declared inline can be applied. The default value is 90. .IP "\fBlarge-function-insns\fR" 4 .IX Item "large-function-insns" The limit specifying really large functions. For functions larger than this limit after inlining inlining is constrained by \&\fB\-\-param large-function-growth\fR. This parameter is useful primarily to avoid extreme compilation time caused by non-linear algorithms used by the backend. This parameter is ignored when \fB\-funit\-at\-a\-time\fR is not used. The default value is 2700. .IP "\fBlarge-function-growth\fR" 4 .IX Item "large-function-growth" Specifies maximal growth of large function caused by inlining in percents. This parameter is ignored when \fB\-funit\-at\-a\-time\fR is not used. The default value is 100 which limits large function growth to 2.0 times the original size. .IP "\fBlarge-unit-insns\fR" 4 .IX Item "large-unit-insns" The limit specifying large translation unit. Growth caused by inlining of units larger than this limit is limited by \fB\-\-param inline-unit-growth\fR. For small units this might be too tight (consider unit consisting of function A that is inline and B that just calls A three time. If B is small relative to A, the growth of unit is 300\e% and yet such inlining is very sane. For very large units consisting of small inlineable functions however the overall unit growth limit is needed to avoid exponential explosion of code size. Thus for smaller units, the size is increased to \fB\-\-param large-unit-insns\fR before applying \fB\-\-param inline-unit-growth\fR. The default is 10000 .IP "\fBinline-unit-growth\fR" 4 .IX Item "inline-unit-growth" Specifies maximal overall growth of the compilation unit caused by inlining. This parameter is ignored when \fB\-funit\-at\-a\-time\fR is not used. The default value is 30 which limits unit growth to 1.3 times the original size. .IP "\fBlarge-stack-frame\fR" 4 .IX Item "large-stack-frame" The limit specifying large stack frames. While inlining the algorithm is trying to not grow past this limit too much. Default value is 256 bytes. .IP "\fBlarge-stack-frame-growth\fR" 4 .IX Item "large-stack-frame-growth" Specifies maximal growth of large stack frames caused by inlining in percents. The default value is 1000 which limits large stack frame growth to 11 times the original size. .IP "\fBmax-inline-insns-recursive\fR" 4 .IX Item "max-inline-insns-recursive" .PD 0 .IP "\fBmax-inline-insns-recursive-auto\fR" 4 .IX Item "max-inline-insns-recursive-auto" .PD Specifies maximum number of instructions out-of-line copy of self recursive inline function can grow into by performing recursive inlining. .Sp For functions declared inline \fB\-\-param max-inline-insns-recursive\fR is taken into account. For function not declared inline, recursive inlining happens only when \fB\-finline\-functions\fR (included in \fB\-O3\fR) is enabled and \fB\-\-param max-inline-insns-recursive-auto\fR is used. The default value is 450. .IP "\fBmax-inline-recursive-depth\fR" 4 .IX Item "max-inline-recursive-depth" .PD 0 .IP "\fBmax-inline-recursive-depth-auto\fR" 4 .IX Item "max-inline-recursive-depth-auto" .PD Specifies maximum recursion depth used by the recursive inlining. .Sp For functions declared inline \fB\-\-param max-inline-recursive-depth\fR is taken into account. For function not declared inline, recursive inlining happens only when \fB\-finline\-functions\fR (included in \fB\-O3\fR) is enabled and \fB\-\-param max-inline-recursive-depth-auto\fR is used. The default value is 8. .IP "\fBmin-inline-recursive-probability\fR" 4 .IX Item "min-inline-recursive-probability" Recursive inlining is profitable only for function having deep recursion in average and can hurt for function having little recursion depth by increasing the prologue size or complexity of function body to other optimizers. .Sp When profile feedback is available (see \fB\-fprofile\-generate\fR) the actual recursion depth can be guessed from probability that function will recurse via given call expression. This parameter limits inlining only to call expression whose probability exceeds given threshold (in percents). The default value is 10. .IP "\fBinline-call-cost\fR" 4 .IX Item "inline-call-cost" Specify cost of call instruction relative to simple arithmetics operations (having cost of 1). Increasing this cost disqualifies inlining of non-leaf functions and at the same time increases size of leaf function that is believed to reduce function size by being inlined. In effect it increases amount of inlining for code having large abstraction penalty (many functions that just pass the arguments to other functions) and decrease inlining for code with low abstraction penalty. The default value is 12. .IP "\fBmin-vect-loop-bound\fR" 4 .IX Item "min-vect-loop-bound" The minimum number of iterations under which a loop will not get vectorized when \fB\-ftree\-vectorize\fR is used. The number of iterations after vectorization needs to be greater than the value specified by this option to allow vectorization. The default value is 0. .IP "\fBmax-unrolled-insns\fR" 4 .IX Item "max-unrolled-insns" The maximum number of instructions that a loop should have if that loop is unrolled, and if the loop is unrolled, it determines how many times the loop code is unrolled. .IP "\fBmax-average-unrolled-insns\fR" 4 .IX Item "max-average-unrolled-insns" The maximum number of instructions biased by probabilities of their execution that a loop should have if that loop is unrolled, and if the loop is unrolled, it determines how many times the loop code is unrolled. .IP "\fBmax-unroll-times\fR" 4 .IX Item "max-unroll-times" The maximum number of unrollings of a single loop. .IP "\fBmax-peeled-insns\fR" 4 .IX Item "max-peeled-insns" The maximum number of instructions that a loop should have if that loop is peeled, and if the loop is peeled, it determines how many times the loop code is peeled. .IP "\fBmax-peel-times\fR" 4 .IX Item "max-peel-times" The maximum number of peelings of a single loop. .IP "\fBmax-completely-peeled-insns\fR" 4 .IX Item "max-completely-peeled-insns" The maximum number of insns of a completely peeled loop. .IP "\fBmax-completely-peel-times\fR" 4 .IX Item "max-completely-peel-times" The maximum number of iterations of a loop to be suitable for complete peeling. .IP "\fBmax-unswitch-insns\fR" 4 .IX Item "max-unswitch-insns" The maximum number of insns of an unswitched loop. .IP "\fBmax-unswitch-level\fR" 4 .IX Item "max-unswitch-level" The maximum number of branches unswitched in a single loop. .IP "\fBlim-expensive\fR" 4 .IX Item "lim-expensive" The minimum cost of an expensive expression in the loop invariant motion. .IP "\fBiv-consider-all-candidates-bound\fR" 4 .IX Item "iv-consider-all-candidates-bound" Bound on number of candidates for induction variables below that all candidates are considered for each use in induction variable optimizations. Only the most relevant candidates are considered if there are more candidates, to avoid quadratic time complexity. .IP "\fBiv-max-considered-uses\fR" 4 .IX Item "iv-max-considered-uses" The induction variable optimizations give up on loops that contain more induction variable uses. .IP "\fBiv-always-prune-cand-set-bound\fR" 4 .IX Item "iv-always-prune-cand-set-bound" If number of candidates in the set is smaller than this value, we always try to remove unnecessary ivs from the set during its optimization when a new iv is added to the set. .IP "\fBscev-max-expr-size\fR" 4 .IX Item "scev-max-expr-size" Bound on size of expressions used in the scalar evolutions analyzer. Large expressions slow the analyzer. .IP "\fBomega-max-vars\fR" 4 .IX Item "omega-max-vars" The maximum number of variables in an Omega constraint system. The default value is 128. .IP "\fBomega-max-geqs\fR" 4 .IX Item "omega-max-geqs" The maximum number of inequalities in an Omega constraint system. The default value is 256. .IP "\fBomega-max-eqs\fR" 4 .IX Item "omega-max-eqs" The maximum number of equalities in an Omega constraint system. The default value is 128. .IP "\fBomega-max-wild-cards\fR" 4 .IX Item "omega-max-wild-cards" The maximum number of wildcard variables that the Omega solver will be able to insert. The default value is 18. .IP "\fBomega-hash-table-size\fR" 4 .IX Item "omega-hash-table-size" The size of the hash table in the Omega solver. The default value is 550. .IP "\fBomega-max-keys\fR" 4 .IX Item "omega-max-keys" The maximal number of keys used by the Omega solver. The default value is 500. .IP "\fBomega-eliminate-redundant-constraints\fR" 4 .IX Item "omega-eliminate-redundant-constraints" When set to 1, use expensive methods to eliminate all redundant constraints. The default value is 0. .IP "\fBvect-max-version-for-alignment-checks\fR" 4 .IX Item "vect-max-version-for-alignment-checks" The maximum number of runtime checks that can be performed when doing loop versioning for alignment in the vectorizer. See option ftree-vect-loop-version for more information. .IP "\fBvect-max-version-for-alias-checks\fR" 4 .IX Item "vect-max-version-for-alias-checks" The maximum number of runtime checks that can be performed when doing loop versioning for alias in the vectorizer. See option ftree-vect-loop-version for more information. .IP "\fBmax-iterations-to-track\fR" 4 .IX Item "max-iterations-to-track" The maximum number of iterations of a loop the brute force algorithm for analysis of # of iterations of the loop tries to evaluate. .IP "\fBhot-bb-count-fraction\fR" 4 .IX Item "hot-bb-count-fraction" Select fraction of the maximal count of repetitions of basic block in program given basic block needs to have to be considered hot. .IP "\fBhot-bb-frequency-fraction\fR" 4 .IX Item "hot-bb-frequency-fraction" Select fraction of the maximal frequency of executions of basic block in function given basic block needs to have to be considered hot .IP "\fBmax-predicted-iterations\fR" 4 .IX Item "max-predicted-iterations" The maximum number of loop iterations we predict statically. This is useful in cases where function contain single loop with known bound and other loop with unknown. We predict the known number of iterations correctly, while the unknown number of iterations average to roughly 10. This means that the loop without bounds would appear artificially cold relative to the other one. .IP "\fBalign-threshold\fR" 4 .IX Item "align-threshold" Select fraction of the maximal frequency of executions of basic block in function given basic block will get aligned. .IP "\fBalign-loop-iterations\fR" 4 .IX Item "align-loop-iterations" A loop expected to iterate at lest the selected number of iterations will get aligned. .IP "\fBtracer-dynamic-coverage\fR" 4 .IX Item "tracer-dynamic-coverage" .PD 0 .IP "\fBtracer-dynamic-coverage-feedback\fR" 4 .IX Item "tracer-dynamic-coverage-feedback" .PD This value is used to limit superblock formation once the given percentage of executed instructions is covered. This limits unnecessary code size expansion. .Sp The \fBtracer-dynamic-coverage-feedback\fR is used only when profile feedback is available. The real profiles (as opposed to statically estimated ones) are much less balanced allowing the threshold to be larger value. .IP "\fBtracer-max-code-growth\fR" 4 .IX Item "tracer-max-code-growth" Stop tail duplication once code growth has reached given percentage. This is rather hokey argument, as most of the duplicates will be eliminated later in cross jumping, so it may be set to much higher values than is the desired code growth. .IP "\fBtracer-min-branch-ratio\fR" 4 .IX Item "tracer-min-branch-ratio" Stop reverse growth when the reverse probability of best edge is less than this threshold (in percent). .IP "\fBtracer-min-branch-ratio\fR" 4 .IX Item "tracer-min-branch-ratio" .PD 0 .IP "\fBtracer-min-branch-ratio-feedback\fR" 4 .IX Item "tracer-min-branch-ratio-feedback" .PD Stop forward growth if the best edge do have probability lower than this threshold. .Sp Similarly to \fBtracer-dynamic-coverage\fR two values are present, one for compilation for profile feedback and one for compilation without. The value for compilation with profile feedback needs to be more conservative (higher) in order to make tracer effective. .IP "\fBmax-cse-path-length\fR" 4 .IX Item "max-cse-path-length" Maximum number of basic blocks on path that cse considers. The default is 10. .IP "\fBmax-cse-insns\fR" 4 .IX Item "max-cse-insns" The maximum instructions \s-1CSE\s0 process before flushing. The default is 1000. .IP "\fBmax-aliased-vops\fR" 4 .IX Item "max-aliased-vops" Maximum number of virtual operands per function allowed to represent aliases before triggering the alias partitioning heuristic. Alias partitioning reduces compile times and memory consumption needed for aliasing at the expense of precision loss in alias information. The default value for this parameter is 100 for \-O1, 500 for \-O2 and 1000 for \-O3. .Sp Notice that if a function contains more memory statements than the value of this parameter, it is not really possible to achieve this reduction. In this case, the compiler will use the number of memory statements as the value for \fBmax-aliased-vops\fR. .IP "\fBavg-aliased-vops\fR" 4 .IX Item "avg-aliased-vops" Average number of virtual operands per statement allowed to represent aliases before triggering the alias partitioning heuristic. This works in conjunction with \fBmax-aliased-vops\fR. If a function contains more than \fBmax-aliased-vops\fR virtual operators, then memory symbols will be grouped into memory partitions until either the total number of virtual operators is below \fBmax-aliased-vops\fR or the average number of virtual operators per memory statement is below \fBavg-aliased-vops\fR. The default value for this parameter is 1 for \-O1 and \-O2, and 3 for \-O3. .IP "\fBggc-min-expand\fR" 4 .IX Item "ggc-min-expand" \&\s-1GCC\s0 uses a garbage collector to manage its own memory allocation. This parameter specifies the minimum percentage by which the garbage collector's heap should be allowed to expand between collections. Tuning this may improve compilation speed; it has no effect on code generation. .Sp The default is 30% + 70% * (\s-1RAM/1GB\s0) with an upper bound of 100% when \&\s-1RAM\s0 >= 1GB. If \f(CW\*(C`getrlimit\*(C'\fR is available, the notion of \*(L"\s-1RAM\s0\*(R" is the smallest of actual \s-1RAM\s0 and \f(CW\*(C`RLIMIT_DATA\*(C'\fR or \f(CW\*(C`RLIMIT_AS\*(C'\fR. If \&\s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower bound of 30% is used. Setting this parameter and \&\fBggc-min-heapsize\fR to zero causes a full collection to occur at every opportunity. This is extremely slow, but can be useful for debugging. .IP "\fBggc-min-heapsize\fR" 4 .IX Item "ggc-min-heapsize" Minimum size of the garbage collector's heap before it begins bothering to collect garbage. The first collection occurs after the heap expands by \fBggc-min-expand\fR% beyond \fBggc-min-heapsize\fR. Again, tuning this may improve compilation speed, and has no effect on code generation. .Sp The default is the smaller of \s-1RAM/8\s0, \s-1RLIMIT_RSS\s0, or a limit which tries to ensure that \s-1RLIMIT_DATA\s0 or \s-1RLIMIT_AS\s0 are not exceeded, but with a lower bound of 4096 (four megabytes) and an upper bound of 131072 (128 megabytes). If \s-1GCC\s0 is not able to calculate \s-1RAM\s0 on a particular platform, the lower bound is used. Setting this parameter very large effectively disables garbage collection. Setting this parameter and \fBggc-min-expand\fR to zero causes a full collection to occur at every opportunity. .IP "\fBmax-reload-search-insns\fR" 4 .IX Item "max-reload-search-insns" The maximum number of instruction reload should look backward for equivalent register. Increasing values mean more aggressive optimization, making the compile time increase with probably slightly better performance. The default value is 100. .IP "\fBmax-cselib-memory-locations\fR" 4 .IX Item "max-cselib-memory-locations" The maximum number of memory locations cselib should take into account. Increasing values mean more aggressive optimization, making the compile time increase with probably slightly better performance. The default value is 500. .IP "\fBmax-flow-memory-locations\fR" 4 .IX Item "max-flow-memory-locations" Similar as \fBmax-cselib-memory-locations\fR but for dataflow liveness. The default value is 100. .IP "\fBreorder-blocks-duplicate\fR" 4 .IX Item "reorder-blocks-duplicate" .PD 0 .IP "\fBreorder-blocks-duplicate-feedback\fR" 4 .IX Item "reorder-blocks-duplicate-feedback" .PD Used by basic block reordering pass to decide whether to use unconditional branch or duplicate the code on its destination. Code is duplicated when its estimated size is smaller than this value multiplied by the estimated size of unconditional jump in the hot spots of the program. .Sp The \fBreorder-block-duplicate-feedback\fR is used only when profile feedback is available and may be set to higher values than \&\fBreorder-block-duplicate\fR since information about the hot spots is more accurate. .IP "\fBmax-sched-ready-insns\fR" 4 .IX Item "max-sched-ready-insns" The maximum number of instructions ready to be issued the scheduler should consider at any given time during the first scheduling pass. Increasing values mean more thorough searches, making the compilation time increase with probably little benefit. The default value is 100. .IP "\fBmax-sched-region-blocks\fR" 4 .IX Item "max-sched-region-blocks" The maximum number of blocks in a region to be considered for interblock scheduling. The default value is 10. .IP "\fBmax-sched-region-insns\fR" 4 .IX Item "max-sched-region-insns" The maximum number of insns in a region to be considered for interblock scheduling. The default value is 100. .IP "\fBmin-spec-prob\fR" 4 .IX Item "min-spec-prob" The minimum probability (in percents) of reaching a source block for interblock speculative scheduling. The default value is 40. .IP "\fBmax-sched-extend-regions-iters\fR" 4 .IX Item "max-sched-extend-regions-iters" The maximum number of iterations through \s-1CFG\s0 to extend regions. 0 \- disable region extension, N \- do at most N iterations. The default value is 0. .IP "\fBmax-sched-insn-conflict-delay\fR" 4 .IX Item "max-sched-insn-conflict-delay" The maximum conflict delay for an insn to be considered for speculative motion. The default value is 3. .IP "\fBsched-spec-prob-cutoff\fR" 4 .IX Item "sched-spec-prob-cutoff" The minimal probability of speculation success (in percents), so that speculative insn will be scheduled. The default value is 40. .IP "\fBmax-last-value-rtl\fR" 4 .IX Item "max-last-value-rtl" The maximum size measured as number of RTLs that can be recorded in an expression in combiner for a pseudo register as last known value of that register. The default is 10000. .IP "\fBinteger-share-limit\fR" 4 .IX Item "integer-share-limit" Small integer constants can use a shared data structure, reducing the compiler's memory usage and increasing its speed. This sets the maximum value of a shared integer constant. The default value is 256. .IP "\fBmin-virtual-mappings\fR" 4 .IX Item "min-virtual-mappings" Specifies the minimum number of virtual mappings in the incremental \&\s-1SSA\s0 updater that should be registered to trigger the virtual mappings heuristic defined by virtual-mappings-ratio. The default value is 100. .IP "\fBvirtual-mappings-ratio\fR" 4 .IX Item "virtual-mappings-ratio" If the number of virtual mappings is virtual-mappings-ratio bigger than the number of virtual symbols to be updated, then the incremental \&\s-1SSA\s0 updater switches to a full update for those symbols. The default ratio is 3. .IP "\fBssp-buffer-size\fR" 4 .IX Item "ssp-buffer-size" The minimum size of buffers (i.e. arrays) that will receive stack smashing protection when \fB\-fstack\-protection\fR is used. .IP "\fBmax-jump-thread-duplication-stmts\fR" 4 .IX Item "max-jump-thread-duplication-stmts" Maximum number of statements allowed in a block that needs to be duplicated when threading jumps. .IP "\fBmax-fields-for-field-sensitive\fR" 4 .IX Item "max-fields-for-field-sensitive" Maximum number of fields in a structure we will treat in a field sensitive manner during pointer analysis. The default is zero for \-O0, and \-O1 and 100 for \-Os, \-O2, and \-O3. .IP "\fBprefetch-latency\fR" 4 .IX Item "prefetch-latency" Estimate on average number of instructions that are executed before prefetch finishes. The distance we prefetch ahead is proportional to this constant. Increasing this number may also lead to less streams being prefetched (see \fBsimultaneous-prefetches\fR). .IP "\fBsimultaneous-prefetches\fR" 4 .IX Item "simultaneous-prefetches" Maximum number of prefetches that can run at the same time. .IP "\fBl1\-cache\-line\-size\fR" 4 .IX Item "l1-cache-line-size" The size of cache line in L1 cache, in bytes. .IP "\fBl1\-cache\-size\fR" 4 .IX Item "l1-cache-size" The size of L1 cache, in kilobytes. .IP "\fBl2\-cache\-size\fR" 4 .IX Item "l2-cache-size" The size of L2 cache, in kilobytes. .IP "\fBuse-canonical-types\fR" 4 .IX Item "use-canonical-types" Whether the compiler should use the \*(L"canonical\*(R" type system. By default, this should always be 1, which uses a more efficient internal mechanism for comparing types in \*(C+ and Objective\-\*(C+. However, if bugs in the canonical type system are causing compilation failures, set this value to 0 to disable canonical types. .IP "\fBmax-partial-antic-length\fR" 4 .IX Item "max-partial-antic-length" Maximum length of the partial antic set computed during the tree partial redundancy elimination optimization (\fB\-ftree\-pre\fR) when optimizing at \fB\-O3\fR and above. For some sorts of source code the enhanced partial redundancy elimination optimization can run away, consuming all of the memory available on the host machine. This parameter sets a limit on the length of the sets that are computed, which prevents the runaway behaviour. Setting a value of 0 for this paramter will allow an unlimited set length. .IP "\fBsccvn-max-scc-size\fR" 4 .IX Item "sccvn-max-scc-size" Maximum size of a strongly connected component (\s-1SCC\s0) during \s-1SCCVN\s0 processing. If this limit is hit, \s-1SCCVN\s0 processing for the whole function will not be done and optimizations depending on it will be disabled. The default maximum \s-1SCC\s0 size is 10000. .RE .RS 4 .RE .Sh "Options Controlling the Preprocessor" .IX Subsection "Options Controlling the Preprocessor" These options control the C preprocessor, which is run on each C source file before actual compilation. .PP If you use the \fB\-E\fR option, nothing is done except preprocessing. Some of these options make sense only together with \fB\-E\fR because they cause the preprocessor output to be unsuitable for actual compilation. .Sp .RS 4 You can use \fB\-Wp,\fR\fIoption\fR to bypass the compiler driver and pass \fIoption\fR directly through to the preprocessor. If \&\fIoption\fR contains commas, it is split into multiple options at the commas. However, many options are modified, translated or interpreted by the compiler driver before being passed to the preprocessor, and \&\fB\-Wp\fR forcibly bypasses this phase. The preprocessor's direct interface is undocumented and subject to change, so whenever possible you should avoid using \fB\-Wp\fR and let the driver handle the options instead. .Sp \&\fB\-Xpreprocessor\fR \fIoption\fR .Sp Pass \fIoption\fR as an option to the preprocessor. You can use this to supply system-specific preprocessor options which \s-1GCC\s0 does not know how to recognize. .Sp If you want to pass an option that takes an argument, you must use \&\fB\-Xpreprocessor\fR twice, once for the option and once for the argument. .RE .IP "\fB\-D\fR \fIname\fR" 4 .IX Item "-D name" Predefine \fIname\fR as a macro, with definition \f(CW1\fR. .IP "\fB\-D\fR \fIname\fR\fB=\fR\fIdefinition\fR" 4 .IX Item "-D name=definition" The contents of \fIdefinition\fR are tokenized and processed as if they appeared during translation phase three in a \fB#define\fR directive. In particular, the definition will be truncated by embedded newline characters. .Sp If you are invoking the preprocessor from a shell or shell-like program you may need to use the shell's quoting syntax to protect characters such as spaces that have a meaning in the shell syntax. .Sp If you wish to define a function-like macro on the command line, write its argument list with surrounding parentheses before the equals sign (if any). Parentheses are meaningful to most shells, so you will need to quote the option. With \fBsh\fR and \fBcsh\fR, \&\fB\-D'\fR\fIname\fR\fB(\fR\fIargs...\fR\fB)=\fR\fIdefinition\fR\fB'\fR works. .Sp \&\fB\-D\fR and \fB\-U\fR options are processed in the order they are given on the command line. All \fB\-imacros\fR \fIfile\fR and \&\fB\-include\fR \fIfile\fR options are processed after all \&\fB\-D\fR and \fB\-U\fR options. .IP "\fB\-U\fR \fIname\fR" 4 .IX Item "-U name" Cancel any previous definition of \fIname\fR, either built in or provided with a \fB\-D\fR option. .IP "\fB\-undef\fR" 4 .IX Item "-undef" Do not predefine any system-specific or GCC-specific macros. The standard predefined macros remain defined. .IP "\fB\-I\fR \fIdir\fR" 4 .IX Item "-I dir" Add the directory \fIdir\fR to the list of directories to be searched for header files. Directories named by \fB\-I\fR are searched before the standard system include directories. If the directory \fIdir\fR is a standard system include directory, the option is ignored to ensure that the default search order for system directories and the special treatment of system headers are not defeated \&. If \fIdir\fR begins with \f(CW\*(C`=\*(C'\fR, then the \f(CW\*(C`=\*(C'\fR will be replaced by the sysroot prefix; see \fB\-\-sysroot\fR and \fB\-isysroot\fR. .IP "\fB\-o\fR \fIfile\fR" 4 .IX Item "-o file" Write output to \fIfile\fR. This is the same as specifying \fIfile\fR as the second non-option argument to \fBcpp\fR. \fBgcc\fR has a different interpretation of a second non-option argument, so you must use \fB\-o\fR to specify the output file. .IP "\fB\-Wall\fR" 4 .IX Item "-Wall" Turns on all optional warnings which are desirable for normal code. At present this is \fB\-Wcomment\fR, \fB\-Wtrigraphs\fR, \&\fB\-Wmultichar\fR and a warning about integer promotion causing a change of sign in \f(CW\*(C`#if\*(C'\fR expressions. Note that many of the preprocessor's warnings are on by default and have no options to control them. .IP "\fB\-Wcomment\fR" 4 .IX Item "-Wcomment" .PD 0 .IP "\fB\-Wcomments\fR" 4 .IX Item "-Wcomments" .PD Warn whenever a comment-start sequence \fB/*\fR appears in a \fB/*\fR comment, or whenever a backslash-newline appears in a \fB//\fR comment. (Both forms have the same effect.) .IP "\fB\-Wtrigraphs\fR" 4 .IX Item "-Wtrigraphs" Most trigraphs in comments cannot affect the meaning of the program. However, a trigraph that would form an escaped newline (\fB??/\fR at the end of a line) can, by changing where the comment begins or ends. Therefore, only trigraphs that would form escaped newlines produce warnings inside a comment. .Sp This option is implied by \fB\-Wall\fR. If \fB\-Wall\fR is not given, this option is still enabled unless trigraphs are enabled. To get trigraph conversion without warnings, but get the other \&\fB\-Wall\fR warnings, use \fB\-trigraphs \-Wall \-Wno\-trigraphs\fR. .IP "\fB\-Wtraditional\fR" 4 .IX Item "-Wtraditional" Warn about certain constructs that behave differently in traditional and \&\s-1ISO\s0 C. Also warn about \s-1ISO\s0 C constructs that have no traditional C equivalent, and problematic constructs which should be avoided. .IP "\fB\-Wimport\fR" 4 .IX Item "-Wimport" Warn the first time \fB#import\fR is used. .IP "\fB\-Wundef\fR" 4 .IX Item "-Wundef" Warn whenever an identifier which is not a macro is encountered in an \&\fB#if\fR directive, outside of \fBdefined\fR. Such identifiers are replaced with zero. .IP "\fB\-Wunused\-macros\fR" 4 .IX Item "-Wunused-macros" Warn about macros defined in the main file that are unused. A macro is \fIused\fR if it is expanded or tested for existence at least once. The preprocessor will also warn if the macro has not been used at the time it is redefined or undefined. .Sp Built-in macros, macros defined on the command line, and macros defined in include files are not warned about. .Sp \&\fINote:\fR If a macro is actually used, but only used in skipped conditional blocks, then \s-1CPP\s0 will report it as unused. To avoid the warning in such a case, you might improve the scope of the macro's definition by, for example, moving it into the first skipped block. Alternatively, you could provide a dummy use with something like: .Sp .Vb 2 \& #if defined the_macro_causing_the_warning \& #endif .Ve .IP "\fB\-Wendif\-labels\fR" 4 .IX Item "-Wendif-labels" Warn whenever an \fB#else\fR or an \fB#endif\fR are followed by text. This usually happens in code of the form .Sp .Vb 5 \& #if FOO \& ... \& #else FOO \& ... \& #endif FOO .Ve .Sp The second and third \f(CW\*(C`FOO\*(C'\fR should be in comments, but often are not in older programs. This warning is on by default. .IP "\fB\-Werror\fR" 4 .IX Item "-Werror" Make all warnings into hard errors. Source code which triggers warnings will be rejected. .IP "\fB\-Wsystem\-headers\fR" 4 .IX Item "-Wsystem-headers" Issue warnings for code in system headers. These are normally unhelpful in finding bugs in your own code, therefore suppressed. If you are responsible for the system library, you may want to see them. .IP "\fB\-w\fR" 4 .IX Item "-w" Suppress all warnings, including those which \s-1GNU\s0 \s-1CPP\s0 issues by default. .IP "\fB\-pedantic\fR" 4 .IX Item "-pedantic" Issue all the mandatory diagnostics listed in the C standard. Some of them are left out by default, since they trigger frequently on harmless code. .IP "\fB\-pedantic\-errors\fR" 4 .IX Item "-pedantic-errors" Issue all the mandatory diagnostics, and make all mandatory diagnostics into errors. This includes mandatory diagnostics that \s-1GCC\s0 issues without \fB\-pedantic\fR but treats as warnings. .IP "\fB\-M\fR" 4 .IX Item "-M" Instead of outputting the result of preprocessing, output a rule suitable for \fBmake\fR describing the dependencies of the main source file. The preprocessor outputs one \fBmake\fR rule containing the object file name for that source file, a colon, and the names of all the included files, including those coming from \fB\-include\fR or \&\fB\-imacros\fR command line options. .Sp Unless specified explicitly (with \fB\-MT\fR or \fB\-MQ\fR), the object file name consists of the name of the source file with any suffix replaced with object file suffix and with any leading directory parts removed. If there are many included files then the rule is split into several lines using \fB\e\fR\-newline. The rule has no commands. .Sp This option does not suppress the preprocessor's debug output, such as \&\fB\-dM\fR. To avoid mixing such debug output with the dependency rules you should explicitly specify the dependency output file with \&\fB\-MF\fR, or use an environment variable like \&\fB\s-1DEPENDENCIES_OUTPUT\s0\fR. Debug output will still be sent to the regular output stream as normal. .Sp Passing \fB\-M\fR to the driver implies \fB\-E\fR, and suppresses warnings with an implicit \fB\-w\fR. .IP "\fB\-MM\fR" 4 .IX Item "-MM" Like \fB\-M\fR but do not mention header files that are found in system header directories, nor header files that are included, directly or indirectly, from such a header. .Sp This implies that the choice of angle brackets or double quotes in an \&\fB#include\fR directive does not in itself determine whether that header will appear in \fB\-MM\fR dependency output. This is a slight change in semantics from \s-1GCC\s0 versions 3.0 and earlier. .IP "\fB\-MF\fR \fIfile\fR" 4 .IX Item "-MF file" When used with \fB\-M\fR or \fB\-MM\fR, specifies a file to write the dependencies to. If no \fB\-MF\fR switch is given the preprocessor sends the rules to the same place it would have sent preprocessed output. .Sp When used with the driver options \fB\-MD\fR or \fB\-MMD\fR, \&\fB\-MF\fR overrides the default dependency output file. .IP "\fB\-MG\fR" 4 .IX Item "-MG" In conjunction with an option such as \fB\-M\fR requesting dependency generation, \fB\-MG\fR assumes missing header files are generated files and adds them to the dependency list without raising an error. The dependency filename is taken directly from the \&\f(CW\*(C`#include\*(C'\fR directive without prepending any path. \fB\-MG\fR also suppresses preprocessed output, as a missing header file renders this useless. .Sp This feature is used in automatic updating of makefiles. .IP "\fB\-MP\fR" 4 .IX Item "-MP" This option instructs \s-1CPP\s0 to add a phony target for each dependency other than the main file, causing each to depend on nothing. These dummy rules work around errors \fBmake\fR gives if you remove header files without updating the \fIMakefile\fR to match. .Sp This is typical output: .Sp .Vb 1 \& test.o: test.c test.h \& \& test.h: .Ve .IP "\fB\-MT\fR \fItarget\fR" 4 .IX Item "-MT target" Change the target of the rule emitted by dependency generation. By default \s-1CPP\s0 takes the name of the main input file, deletes any directory components and any file suffix such as \fB.c\fR, and appends the platform's usual object suffix. The result is the target. .Sp An \fB\-MT\fR option will set the target to be exactly the string you specify. If you want multiple targets, you can specify them as a single argument to \fB\-MT\fR, or use multiple \fB\-MT\fR options. .Sp For example, \fB\-MT\ '$(objpfx)foo.o'\fR might give .Sp .Vb 1 \& $(objpfx)foo.o: foo.c .Ve .IP "\fB\-MQ\fR \fItarget\fR" 4 .IX Item "-MQ target" Same as \fB\-MT\fR, but it quotes any characters which are special to Make. \fB\-MQ\ '$(objpfx)foo.o'\fR gives .Sp .Vb 1 \& $$(objpfx)foo.o: foo.c .Ve .Sp The default target is automatically quoted, as if it were given with \&\fB\-MQ\fR. .IP "\fB\-MD\fR" 4 .IX Item "-MD" \&\fB\-MD\fR is equivalent to \fB\-M \-MF\fR \fIfile\fR, except that \&\fB\-E\fR is not implied. The driver determines \fIfile\fR based on whether an \fB\-o\fR option is given. If it is, the driver uses its argument but with a suffix of \fI.d\fR, otherwise it takes the name of the input file, removes any directory components and suffix, and applies a \fI.d\fR suffix. .Sp If \fB\-MD\fR is used in conjunction with \fB\-E\fR, any \&\fB\-o\fR switch is understood to specify the dependency output file, but if used without \fB\-E\fR, each \fB\-o\fR is understood to specify a target object file. .Sp Since \fB\-E\fR is not implied, \fB\-MD\fR can be used to generate a dependency output file as a side-effect of the compilation process. .IP "\fB\-MMD\fR" 4 .IX Item "-MMD" Like \fB\-MD\fR except mention only user header files, not system header files. .IP "\fB\-fpch\-deps\fR" 4 .IX Item "-fpch-deps" When using precompiled headers, this flag will cause the dependency-output flags to also list the files from the precompiled header's dependencies. If not specified only the precompiled header would be listed and not the files that were used to create it because those files are not consulted when a precompiled header is used. .IP "\fB\-fpch\-preprocess\fR" 4 .IX Item "-fpch-preprocess" This option allows use of a precompiled header together with \fB\-E\fR. It inserts a special \f(CW\*(C`#pragma\*(C'\fR, \&\f(CW\*(C`#pragma GCC pch_preprocess ""\*(C'\fR in the output to mark the place where the precompiled header was found, and its filename. When \&\fB\-fpreprocessed\fR is in use, \s-1GCC\s0 recognizes this \f(CW\*(C`#pragma\*(C'\fR and loads the \s-1PCH\s0. .Sp This option is off by default, because the resulting preprocessed output is only really suitable as input to \s-1GCC\s0. It is switched on by \&\fB\-save\-temps\fR. .Sp You should not write this \f(CW\*(C`#pragma\*(C'\fR in your own code, but it is safe to edit the filename if the \s-1PCH\s0 file is available in a different location. The filename may be absolute or it may be relative to \s-1GCC\s0's current directory. .IP "\fB\-x c\fR" 4 .IX Item "-x c" .PD 0 .IP "\fB\-x c++\fR" 4 .IX Item "-x c++" .IP "\fB\-x objective-c\fR" 4 .IX Item "-x objective-c" .IP "\fB\-x assembler-with-cpp\fR" 4 .IX Item "-x assembler-with-cpp" .PD Specify the source language: C, \*(C+, Objective-C, or assembly. This has nothing to do with standards conformance or extensions; it merely selects which base syntax to expect. If you give none of these options, cpp will deduce the language from the extension of the source file: \&\fB.c\fR, \fB.cc\fR, \fB.m\fR, or \fB.S\fR. Some other common extensions for \*(C+ and assembly are also recognized. If cpp does not recognize the extension, it will treat the file as C; this is the most generic mode. .Sp \&\fINote:\fR Previous versions of cpp accepted a \fB\-lang\fR option which selected both the language and the standards conformance level. This option has been removed, because it conflicts with the \fB\-l\fR option. .IP "\fB\-std=\fR\fIstandard\fR" 4 .IX Item "-std=standard" .PD 0 .IP "\fB\-ansi\fR" 4 .IX Item "-ansi" .PD Specify the standard to which the code should conform. Currently \s-1CPP\s0 knows about C and \*(C+ standards; others may be added in the future. .Sp \&\fIstandard\fR may be one of: .RS 4 .ie n .IP """iso9899:1990""" 4 .el .IP "\f(CWiso9899:1990\fR" 4 .IX Item "iso9899:1990" .PD 0 .ie n .IP """c89""" 4 .el .IP "\f(CWc89\fR" 4 .IX Item "c89" .PD The \s-1ISO\s0 C standard from 1990. \fBc89\fR is the customary shorthand for this version of the standard. .Sp The \fB\-ansi\fR option is equivalent to \fB\-std=c89\fR. .ie n .IP """iso9899:199409""" 4 .el .IP "\f(CWiso9899:199409\fR" 4 .IX Item "iso9899:199409" The 1990 C standard, as amended in 1994. .ie n .IP """iso9899:1999""" 4 .el .IP "\f(CWiso9899:1999\fR" 4 .IX Item "iso9899:1999" .PD 0 .ie n .IP """c99""" 4 .el .IP "\f(CWc99\fR" 4 .IX Item "c99" .ie n .IP """iso9899:199x""" 4 .el .IP "\f(CWiso9899:199x\fR" 4 .IX Item "iso9899:199x" .ie n .IP """c9x""" 4 .el .IP "\f(CWc9x\fR" 4 .IX Item "c9x" .PD The revised \s-1ISO\s0 C standard, published in December 1999. Before publication, this was known as C9X. .ie n .IP """gnu89""" 4 .el .IP "\f(CWgnu89\fR" 4 .IX Item "gnu89" The 1990 C standard plus \s-1GNU\s0 extensions. This is the default. .ie n .IP """gnu99""" 4 .el .IP "\f(CWgnu99\fR" 4 .IX Item "gnu99" .PD 0 .ie n .IP """gnu9x""" 4 .el .IP "\f(CWgnu9x\fR" 4 .IX Item "gnu9x" .PD The 1999 C standard plus \s-1GNU\s0 extensions. .ie n .IP """c++98""" 4 .el .IP "\f(CWc++98\fR" 4 .IX Item "c++98" The 1998 \s-1ISO\s0 \*(C+ standard plus amendments. .ie n .IP """gnu++98""" 4 .el .IP "\f(CWgnu++98\fR" 4 .IX Item "gnu++98" The same as \fB\-std=c++98\fR plus \s-1GNU\s0 extensions. This is the default for \*(C+ code. .RE .RS 4 .RE .IP "\fB\-I\-\fR" 4 .IX Item "-I-" Split the include path. Any directories specified with \fB\-I\fR options before \fB\-I\-\fR are searched only for headers requested with \&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for \&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR. If additional directories are specified with \fB\-I\fR options after the \fB\-I\-\fR, those directories are searched for all \fB#include\fR directives. .Sp In addition, \fB\-I\-\fR inhibits the use of the directory of the current file directory as the first search directory for \f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR. This option has been deprecated. .IP "\fB\-nostdinc\fR" 4 .IX Item "-nostdinc" Do not search the standard system directories for header files. Only the directories you have specified with \fB\-I\fR options (and the directory of the current file, if appropriate) are searched. .IP "\fB\-nostdinc++\fR" 4 .IX Item "-nostdinc++" Do not search for header files in the \*(C+\-specific standard directories, but do still search the other standard directories. (This option is used when building the \*(C+ library.) .IP "\fB\-include\fR \fIfile\fR" 4 .IX Item "-include file" Process \fIfile\fR as if \f(CW\*(C`#include "file"\*(C'\fR appeared as the first line of the primary source file. However, the first directory searched for \fIfile\fR is the preprocessor's working directory \fIinstead of\fR the directory containing the main source file. If not found there, it is searched for in the remainder of the \f(CW\*(C`#include "..."\*(C'\fR search chain as normal. .Sp If multiple \fB\-include\fR options are given, the files are included in the order they appear on the command line. .IP "\fB\-imacros\fR \fIfile\fR" 4 .IX Item "-imacros file" Exactly like \fB\-include\fR, except that any output produced by scanning \fIfile\fR is thrown away. Macros it defines remain defined. This allows you to acquire all the macros from a header without also processing its declarations. .Sp All files specified by \fB\-imacros\fR are processed before all files specified by \fB\-include\fR. .IP "\fB\-idirafter\fR \fIdir\fR" 4 .IX Item "-idirafter dir" Search \fIdir\fR for header files, but do it \fIafter\fR all directories specified with \fB\-I\fR and the standard system directories have been exhausted. \fIdir\fR is treated as a system include directory. If \fIdir\fR begins with \f(CW\*(C`=\*(C'\fR, then the \f(CW\*(C`=\*(C'\fR will be replaced by the sysroot prefix; see \fB\-\-sysroot\fR and \fB\-isysroot\fR. .IP "\fB\-iprefix\fR \fIprefix\fR" 4 .IX Item "-iprefix prefix" Specify \fIprefix\fR as the prefix for subsequent \fB\-iwithprefix\fR options. If the prefix represents a directory, you should include the final \fB/\fR. .IP "\fB\-iwithprefix\fR \fIdir\fR" 4 .IX Item "-iwithprefix dir" .PD 0 .IP "\fB\-iwithprefixbefore\fR \fIdir\fR" 4 .IX Item "-iwithprefixbefore dir" .PD Append \fIdir\fR to the prefix specified previously with \&\fB\-iprefix\fR, and add the resulting directory to the include search path. \fB\-iwithprefixbefore\fR puts it in the same place \fB\-I\fR would; \fB\-iwithprefix\fR puts it where \fB\-idirafter\fR would. .IP "\fB\-isysroot\fR \fIdir\fR" 4 .IX Item "-isysroot dir" This option is like the \fB\-\-sysroot\fR option, but applies only to header files. See the \fB\-\-sysroot\fR option for more information. .IP "\fB\-imultilib\fR \fIdir\fR" 4 .IX Item "-imultilib dir" Use \fIdir\fR as a subdirectory of the directory containing target-specific \*(C+ headers. .IP "\fB\-isystem\fR \fIdir\fR" 4 .IX Item "