[Compbench-devel] CompBenchmarks++/libcompbenchmarks/share/KB/gxx/3.0.x description.xml, 1.1, 1.2
Brought to you by:
xfred
Menu
▾
▴
[Compbench-devel] CompBenchmarks++/libcompbenchmarks/share/KB/gxx/3.0.x description.xml, 1.1, 1.2 options.xml, 1.1, 1.2
|
From: Frederic T. <xf...@us...> - 2007-04-10 08:35:40
|
Update of /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx/3.0.x In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv2602 Modified Files: description.xml options.xml Log Message: Varions improvements. Index: options.xml =================================================================== RCS file: /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx/3.0.x/options.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** options.xml 4 Apr 2007 18:32:46 -0000 1.1 --- options.xml 9 Apr 2007 10:12:06 -0000 1.2 *************** *** 108,111 **** --- 108,192 ---- </cel-cond-if> </cel-cond-if> + + <cel-cond-if> + <cel-cmp-eq> + <cel-var-get> + <cel-str>return</cel-str> + </cel-var-get> + <cel-str>1</cel-str> + <cel-var-set> + <cel-str>kb-option-ssa-enabled</cel-str> + <cel-str>1</cel-str> + </cel-var-set> + </cel-cond-if> + + + <cel-var-get> + <cel-str>return</cel-str> + </cel-var-get> + </cel-function-def> + + <!-- dce (Dead-Code Elimination in SSA form) --> + <cel-function-def> + <cel-str>kb-gxx-option-dce-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc3.0-is-compatible</cel-str> + </cel-function-call> + </cel-var-set> + + <cel-cond-if> + <cel-cmp-eq> + <cel-var-get> + <cel-str>return</cel-str> + </cel-var-get> + <cel-str>1</cel-str> + </cel-cmp-eq> + <cel-cond-if> + <cel-cmp-eq> + <cel-var-get> + <cel-str>kb-option-ssa-enabled</cel-str> + </cel-var-get> + <cel-str>1</cel-str> + </cel-cmp-eq> + !!!<!!! + <cel-str>kb-option-ssa-enabled</cel-str> + <cel-str>1</cel-str> + </cel-var-set> + </cel-cond-if> + + + + + <cel-cond-if> + <cel-cmp-eq> + <cel-var-get> + <cel-str>return</cel-str> + </cel-var-get> + <cel-str>1</cel-str> + </cel-cmp-eq> + <cel-cond-if> + <cel-logic-or> + <cel-cmp-eq> + <cel-var-get> + <cel-str>kb-option-mainoptimization</cel-str> + </cel-var-get> + <cel-str>-O2</cel-str> + </cel-cmp-eq> + <cel-cmp-eq> + <cel-var-get> + <cel-str>kb-option-mainoptimization</cel-str> + </cel-var-get> + <cel-str>-O3</cel-str> + </cel-cmp-eq> + </cel-logic-or> + <cel-var-set> + <cel-str>return</cel-str> + <cel-str>option implied by -O2 and -O3</cel-str> + </cel-var-set> + </cel-cond-if> + </cel-cond-if> <cel-var-get> <cel-str>return</cel-str> Index: description.xml =================================================================== RCS file: /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx/3.0.x/description.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** description.xml 4 Apr 2007 18:32:46 -0000 1.1 --- description.xml 9 Apr 2007 10:12:06 -0000 1.2 *************** *** 22,36 **** Users should not specify this option, since it is not yet ready for production use. </editor-description> </option> ! <!-- ! <option id=""> ! <value></value> ! <short-description></short-description> <editor-description> </editor-description> </option> - --> </options> \ No newline at end of file --- 22,150 ---- Users should not specify this option, since it is not yet ready for production use. + According to -fdce description, this is probably an experimental feature. </editor-description> </option> ! <option id="fdce"> ! <value>-fdce</value> ! <short-description>Dead-code elimination in SSA form</short-description> <editor-description> + Perform dead-code elimination in SSA form. Requires -fssa. Like + -fssa, this is an experimental feature. + </editor-description> + </option> + + <option id="no-align-functions"> + <value>-falign-functions=1</value> + <short-description>Disable start of functions offset alignment</short-description> + <editor-description> + Align the start of functions to the next power-of-two greater than + n, skipping up to n bytes. For instance, -falign-functions=32 + aligns functions to the next 32-byte boundary, + but -falign-functions=24 would align to the next 32-byte boundary + only if this can be done by skipping 23 bytes or less. + + -fno-align-functions and -falign-functions=1 are equivalent and + mean that functions will not be aligned. + + Some assemblers only support this flag when n is a power of two; in + that case, it is rounded up. + + If n is not specified, use a machine-dependent default. + </editor-description> + </option> + + <option id="align-functions"> + <value>-falign-functions</value> + <short-description>Force start of functions alignment to machine default</short-description> + <editor-description> + Align the start of functions to the next power-of-two greater than + n, skipping up to n bytes. For instance, -falign-functions=32 + aligns functions to the next 32-byte boundary, + but -falign-functions=24 would align to the next 32-byte boundary + only if this can be done by skipping 23 bytes or less. + + -fno-align-functions and -falign-functions=1 are equivalent and + mean that functions will not be aligned. + + Some assemblers only support this flag when n is a power of two; in + that case, it is rounded up. + + If n is not specified, use a machine-dependent default. + </editor-description> + </option> + + <option id="no-align-labels"> + <value>-falign-labels=1</value> + <short-description>Disable branch targets alignment</short-description> + <editor-description> + Align all branch targets to a power-of-two boundary, skipping up to + n bytes like -falign-functions. This option can easily make code + slower, because it must insert dummy operations for when the branch + target is reached in the usual flow of the code. + + If -falign-loops or -falign-jumps are applicable and are greater + than this value, then their values are used instead. + + If n is not specified, use a machine-dependent default which is + very likely to be 1, meaning no alignment. + </editor-description> + </option> + + <option id="align-labels"> + <value>-falign-labels</value> + <short-description>Align branch targets on machine-default boundaries</short-description> + <editor-description> + Align all branch targets to a power-of-two boundary, skipping up to + n bytes like -falign-functions. This option can easily make code + slower, because it must insert dummy operations for when the branch + target is reached in the usual flow of the code. + + If -falign-loops or -falign-jumps are applicable and are greater + than this value, then their values are used instead. + + If n is not specified, use a machine-dependent default which is + very likely to be 1, meaning no alignment. + </editor-description> + </option> + + <option id="no-align-loops"> + <value>-falign-loops=1</value> + <short-description>Disable loops alignment</short-description> + <editor-description> + Align loops to a power-of-two boundary, skipping up to n bytes like + -falign-functions. The hope is that the loop will be executed many + times, which will make up for any execution of the dummy opera- + tions. + + If n is not specified, use a machine-dependent default. + </editor-description> + </option> + + <option id="align-loops"> + <value>-falign-loops</value> + <short-description>Set loops alignment to machine-default</short-description> + <editor-description> + Align loops to a power-of-two boundary, skipping up to n bytes like + -falign-functions. The hope is that the loop will be executed many + times, which will make up for any execution of the dummy opera- + tions. + + If n is not specified, use a machine-dependent default. + </editor-description> + </option> + + <option id="no-align-jumps"> + <value>-falign-jumps=1</value> + <short-description>Disable branch target alignment</short-description> + <editor-description> + Align branch targets to a power-of-two boundary, for branch targets + where the targets can only be reached by jumping, skipping up to n + bytes like -falign-functions. In this case, no dummy operations + need be executed. + + If n is not specified, use a machine-dependent default. </editor-description> </option> </options> \ No newline at end of file |
