[Compbench-devel] CompBenchmarks++/libcompbenchmarks/share/KB/gxx cse.xml, 1.1, 1.2 description.xml
Brought to you by:
xfred
Menu
▾
▴
[Compbench-devel] CompBenchmarks++/libcompbenchmarks/share/KB/gxx cse.xml, 1.1, 1.2 description.xml, 1.1, 1.2 options.xml, 1.1, 1.2
|
From: Frederic T. <xf...@us...> - 2007-03-13 20:27:36
|
Update of /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv27562 Modified Files: cse.xml description.xml options.xml Log Message: More supported options. Index: options.xml =================================================================== RCS file: /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx/options.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** options.xml 13 Mar 2007 17:42:10 -0000 1.1 --- options.xml 13 Mar 2007 20:27:32 -0000 1.2 *************** *** 6,9 **** --- 6,12 ---- <cel-str>gxx/mainopt.xml</cel-str> <cel-str>gxx/cse.xml</cel-str> + <cel-str>gxx/inline.xml</cel-str> + <cel-str>gxx/loops.xml</cel-str> + <cel-str>gxx/arch.xml</cel-str> </cel-include> *************** *** 208,211 **** --- 211,347 ---- </cel-function-def> + <!-- float-store --> + <cel-function-def> + <cel-str>kb-gxx-option-float-store-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-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-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> + </cel-var-get> + </cel-function-def> + + + <!-- force-addr --> + <cel-function-def> + <cel-str>kb-gxx-option-force-addr-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-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-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> + </cel-var-get> + </cel-function-def> + + <!-- force-mem --> + <cel-function-def> + <cel-str>kb-gxx-option-force-mem-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-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-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> + </cel-var-get> + </cel-function-def> + <!-- fast-math --> <cel-function-def> *************** *** 217,219 **** --- 353,455 ---- </cel-function-def> + <!-- Not integrated (seem useless for optimizations measurement : --> + <!-- no-defer-pop, no-peephole --> + + <!-- omit-frame-pointer --> + <cel-function-def> + <cel-str>kb-gxx-option-omit-frame-pointer-is-compatible</cel-str> + + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-is-compatible</cel-str> + </cel-function-call> + </cel-function-def> + + <!-- schedule-insns --> + <cel-function-def> + <cel-str>kb-gxx-option-schedule-insns-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-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-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> + </cel-var-get> + </cel-function-def> + + <!-- schedule-insns2 --> + <cel-function-def> + <cel-str>kb-gxx-option-schedule-insns2-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-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-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> + </cel-var-get> + </cel-function-def> + </cel> Index: description.xml =================================================================== RCS file: /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx/description.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** description.xml 13 Mar 2007 17:42:10 -0000 1.1 --- description.xml 13 Mar 2007 20:27:32 -0000 1.2 *************** *** 160,163 **** --- 160,360 ---- </option> + <option id="float-store"> + <value>-ffloat-store</value> + <short-description>Do not store floating point variables in registers</short-description> + <editor-description> + Do not store floating point variables in registers. This prevents + undesirable excess precision on machines such as the 68000 + where the floating registers (of the 68881) keep more precision + than a double is supposed to have. + + For most programs, the excess precision does only good, but a + few programs rely on the precise definition of IEEE floating + point. Use `-ffloat-store' for such programs. + </editor-description> + </option> + + <option id="force-addr"> + <value>-fforce-addr</value> + <short-description>Force memory address constants to be copied in registers</short-description> + <editor-description> + Force memory address constants to be copied into registers before + doing arithmetic on them. This may produce better code + just as `-fforce-mem' may. I am interested in hearing about the + difference this makes. + </editor-description> + </option> + + <option id="force-mem"> + <value>-fforce-mem</value> + <short-description>Force memory operands to be copied into registers</short-description> + <editor-description> + Force memory operands to be copied into registers before doing + arithmetic on them. This may produce better code by making all + memory references potential common subexpressions. When they + are not common subexpressions, instruction combination should + eliminate the separate register-load. I am interested in hearing + about the difference this makes. + </editor-description> + </option> + + <option id="inline-functions"> + <value>-finline-functions</value> + <short-description>Integrate all simple functions into their callers</short-description> + <editor-description> + Integrate all simple functions into their callers. The compiler + heuristically decides which functions are simple enough to be + worth integrating in this way. + + If all calls to a given function are integrated, and the function + is declared static, then GCC normally does not output the + function as assembler code in its own right. + </editor-description> + </option> + + <option id="omit-frame-pointer"> + <value>-fomit-frame-pointer</value> + <short-description>Remove frame pointer from register when useless</short-description> + <editor-description> + Don't keep the frame pointer in a register for functions that + don't need one. This avoids the instructions to save, set up + and restore frame pointers; it also makes an extra register + available in many functions. It also makes debugging impossible + on most machines. + + On some machines, such as the Vax, this flag has no effect, because + the standard calling sequence automatically handles the + frame pointer and nothing is saved by pretending it doesn't exist. + The machine-description macro FRAME_POINTER_REQUIRED controls + whether a target machine supports this flag. + </editor-description> + </option> + + <option id="rerun-cse-after-loop"> + <value>-frerun-cse-after-loop</value> + <short-description>Re-run CSE after loop optimizations</short-description> + <editor-description> + Re-run common subexpression elimination after loop optimizations + has been performed. + </editor-description> + </option> + + <option id="schedule-insns"> + <value>-fschedule-insns</value> + <short-description>Attempt to reorder instructions to eliminate stalls</short-description> + <editor-description> + If supported for the target machine, attempt to reorder instructions + to eliminate execution stalls due to required data being + unavailable. This helps machines that have slow floating point + or memory load instructions by allowing other instructions to be + issued until the result of the load or floating point instruction + is required. + </editor-description> + </option> + + <option id="schedule-insns2"> + <value>-fschedule-insns2</value> + <short-description>Attempt to reorder instructions to eliminate stalls (also watch for registers)</short-description> + <editor-description> + Similar to `-fschedule-insns', but requests an additional pass + of instruction scheduling after register allocation has been + done. This is especially useful on machines with a relatively + small number of registers and where memory load instructions + take more than one cycle. + </editor-description> + </option> + + <option id="strength-reduce"> + <value>-fstrength-reduce</value> + <short-description>Loop optimizations</short-description> + <editor-description> + Perform the optimizations of loop strength reduction and + elimination of iteration variables. + </editor-description> + </option> + + <option id="thread-jumps"> + <value>-fthread-jumps</value> + <short-description>Jump shortcuts' detection</short-description> + <editor-description> + Perform optimizations where we check to see if a jump branches + to a location where another comparison subsumed by the first is + found. If so, the first branch is redirected to either the + destination of the second branch or a point immediately following + it, depending on whether the condition is known to be true or + false. + </editor-description> + </option> + + + <option id="unroll-all-loops"> + <value>-funroll-all-loops</value> + <short-description>Global loop unrolling optimization</short-description> + <editor-description> + Perform the optimization of loop unrolling. This is done for + all loops. This usually makes programs run more slowly. + </editor-description> + </option> + + + <option id="unroll-loops"> + <value>-funroll-loops</value> + <short-description>Loop unrolling optimizations</short-description> + <editor-description> + Perform the optimization of loop unrolling. This is only done + for loops whose number of iterations can be determined at com- + pile time or run time. + </editor-description> + </option> + + <option id="m486"> + <value>-m486</value> + <short-description>Generate i486 optimized code</short-description> + <editor-description> + Control whether or not code is optimized for a 486 instead of an + 386. Code generated for a 486 will run on a 386 and vice versa. + </editor-description> + </option> + + + <option id="no-fp-ret-in-387"> + <value>-fno-fp-ret-in-387</value> + <short-description>Do not use FPU to return values</short-description> + <editor-description> + Do not use the FPU registers for return values of functions. + + The usual calling convention has functions return values of + types float and double in an FPU register, even if there is no + FPU. The idea is that the operating system should emulate an + FPU. + + The option `-mno-fp-ret-in-387' causes such values to be + returned in ordinary CPU registers instead. + </editor-description> + </option> + + + <option id=""> + <value></value> + <short-description></short-description> + <editor-description> + </editor-description> + </option> + + + <option id=""> + <value></value> + <short-description></short-description> + <editor-description> + </editor-description> + </option> + + <option id=""> + <value></value> + <short-description></short-description> + <editor-description> + </editor-description> + </option> + <option id=""> <value></value> *************** *** 194,196 **** --- 391,394 ---- </editor-description> </option> + </options> \ No newline at end of file Index: cse.xml =================================================================== RCS file: /cvsroot/compbench/CompBenchmarks++/libcompbenchmarks/share/KB/gxx/cse.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** cse.xml 13 Mar 2007 17:42:10 -0000 1.1 --- cse.xml 13 Mar 2007 20:27:32 -0000 1.2 *************** *** 93,95 **** --- 93,139 ---- </cel-var-get> </cel-function-def> + + <!-- rerun-cse-after-loop --> + <cel-function-def> + <cel-str>kb-gxx-option-rerun-cse-after-loop-is-compatible</cel-str> + + <cel-var-set> + <cel-str>return</cel-str> + <cel-function-call> + <cel-str>kb-gxx-option-gcc2.95-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-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> + </cel-var-get> + </cel-function-def> </cel> \ No newline at end of file |
