Lines Matching refs:is
16 performance indication which is more meaningful than MIPS numbers
21 function. Version 2 of Dhrystone is the result of such a re-
31 There is an obvious need for a common C version of Dhrystone, since C
32 is at present the most popular system programming language for the
34 Dhrystone is used most. There should be, as far as possible, only
43 o As far as it is possible without changes to the Dhrystone statistics,
93 However, it turned out that it is not enough just to inclose the main
95 the variables that are computed are not used somehow, there is the
103 branches that are not executed. The intention is that optimizing
116 To a certain degree, this is unavoidable for small synthetic
118 whether code is generated for all statements of Dhrystone.
124 makes the program simpler.) However, since the loop check is now part
166 variable (Bool_Loc); Bool_Loc would be a "dead variable" which is not
178 ('R' instead of 'X') because a comparison with 'X' is implied in the
188 "else" part, it is considered bad programming practice if a function
206 represented in the program, and that execution time is dominated by
211 It should be noted that this is a language-dependent issue: Dhrystone
213 spent in the string operations is, at least in all implementations
224 the length of the strings is not known at compilation time; the
230 don't think that this is unfair since string functions do occur quite
241 When Dhrystone is used, the following "ground rules" apply:
248 is intended, as is the distribution of inter-module and intra-module
251 compilation units are merged into one file, the rule is that separate
252 compilation should be used. The intention is that real programming
258 larger, the intention is that these effects of separate compilation
262 (e.g., final register allocation is performed after linkage). This
263 is a borderline case: Post-linkage optimization involves additional
280 expansion of procedures), procedure merging is not to be used. The
281 reason is that the percentage of procedure and function calls is part
291 It is often hard to draw an exact line between "normal code
294 optimization is explicitly requested. Also, we cannot avoid that in
298 times are measured. Dhrystone is not intended to be non-optimizable
299 but is intended to be similarly optimizable as normal programs. For
307 the same hardware is encouraged.
327 feeling how much performance difference is due to compiler optimization
328 and how much is due to hardware speed.