Lines Matching refs:that

26   However, the version that was used most often  for  benchmarking  has
35   one C version of Dhrystone such that results can be compared  without
45   statements.  It has turned out in the past that optimizing  compilers
48   danger  that  benchmarking results obtained by a naive application of
49   Dhrystone - without inspection of the code that was generated - could
52 The overall policiy for version 2 has been  that  the  distribution  of
64 of representative programs that can be used as benchmarks; users should
76 In general, version 2 follows - in the parts that are  significant  for
81 Reinhold  Weicker.  (However,  the  differences have been so small that
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
96 danger  that  the  compiler  considers  them  as  "dead  variables" and
103 branches  that  are  not  executed.  The  intention  is that optimizing
105 loop,  or  from  removing code altogether. Statements that are executed
107 role  of  some operands has been changed, and it was made sure that the
113 Because of the self-imposed limitation that the order and  distribution
130 In this section, all changes are described that affect the  measurement
131 loop and that are not just renamings of variables. All remarks refer to
205 There has been some  concern  that  the  string  operations  are  over-
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
230 don't think that this is unfair since string functions do  occur  quite
235 I admit that the string comparison in Dhrystone terminates later (after
251   compilation units are merged into one file, the rule is that separate
252   compilation  should  be used.  The intention is that real programming
254   units, should be reflected.  This also has implies that the compiler,
258   larger,  the  intention is that these effects of separate compilation
266   think that since it defeats the intentions given above, it should not
281   reason is that the percentage of procedure and function calls is part
293   operations by default that are invoked in other compilers  only  when
294   optimization  is explicitly requested.  Also, we cannot avoid that in
295   benchmarking people try to achieve  results  that  look  as  good  as