Lines Matching refs:not

38   not significant) differences.
91 The original publication of Dhrystone did not  contain  any  statements
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
114 of the executed statements should not be changed, there are still cases
115 where optimizing compilers may not generate code for  some  statements.
131 loop and that are not just renamings of variables. All remarks refer to
146   (This probably will not happen for the C version, but it  did  happen
166   variable (Bool_Loc); Bool_Loc would be a "dead variable" which is not
187   statement.   While  the  program  would not be incorrect without this
202 not  been  changed,  to  keep  the program consistent with the original
219 are not part  of  the  language,  so  the  string  operations  must  be
224 the  length  of  the  strings  is  not  known  at compilation time; the
264   program  preparation time (although not as much as compilation in one
266   think that since it defeats the intentions given above, it should not
269   Unfortunately, ISO/ANSI Pascal does not contain language features for
272   Dhrystone  since such a version would not be portable.  Therefore, no
280   expansion of procedures), procedure merging is not to be  used.   The
283   restriction  does  not hold for the string functions of the C version
297   than those listed above - are not forbidden when Dhrystone  execution
298   times  are measured.  Dhrystone is not intended to be non-optimizable