Lines Matching refs:statements

54 -  statements.  It has  turned  out  in  the  past  that  optimizing  compilers
55 -  suppressed  code  generation for too many statements (by "dead code removal"
61 -statements,  operand types and operand locality described in [1] should remain
63 -should be negligible.)  Also, the order of statements should remain unchanged.
97 -The original publication of Dhrystone did not contain any statements for  time
102 -"dead  variables" and suppresses code generation for a part of the statements.
113 -(distribution of statements, operand types and locality) still hold as much as
118 -executed  statements  should  not  be  changed,  there  are  still cases where
119 -optimizing compilers may not generate code for some statements. To  a  certain
122 -statements of Dhrystone.
139 -In addition to adding  the  measurement  loop  and  the  printout  statements,
142 -o In procedure "main", three statements have been added  in  the  non-executed
295 -  statements contained in [1].  This restriction does not hold for the  string
474 -marketing  statements.  For serious performance evaluation, it is necessary to
484 -Dhrystone contains two statements  where  the  programming  language  and  its
633 - *              on which the distribution of statements etc. is based.
681 - *              removing significant statements.
705 - *              loop, or from removing code altogether. Since the statements
708 - *              (distribution of statements, operand types and locality)
724 - *              distribution of the executed statements should not be
726 - *              may not generate code for some statements. To a certain
729 - *              whether code is generated for all statements of Dhrystone.
808 - *  The following program contains statements of a high level programming
812 - *    control statements           33 (32.4 %)
815 - *  103 statements are dynamically executed. The program is balanced with