Please confirm the information below before signing in. Already have an account? Sign In.
Please wait you will be redirected shortly.
We've sent an email with instructions to create a new password. Your existing password has not been changed.
Sorry, we could not verify that email address. Enter your email below, and we'll send you another email.
Check your email for a link to verify your email address.
Thank you for verifiying your email address.
Your password has been successfully updated.
We didn't recognize that password reset code. Enter your email below, and we'll send you another email.
We've sent you an email with instructions to create a new password. Your existing password has not been changed.
Return to Article
...optimizing compilers should be prevented from removing significant statements. It has turned out in the past that optimizing compilers suppressed code generation for too many statements (by "dead code removal" or "dead variable elimination"). This has lead to the danger that benchmarking results obtained by a naive application of Dhrystone - without inspection of the code that was generated - could become meaningless.[http://bit.ly/1atTdWZ]