|Expensive bounds checking (was: Unsafe Optimizations email@example.com (1990-06-15)|
|Re: Expensive bounds checking (was: Unsafe Optimizations firstname.lastname@example.org (1990-06-15)|
|From:||email@example.com (Jan Prins)|
|Date:||Fri, 15 Jun 90 05:20:29 GMT|
|Organization:||University of North Carolina, Chapel Hill|
|Keywords:||superscalar, bounds checking|
James Larus writes in <1990Jun14.firstname.lastname@example.org>:
> [discussion of Gupta's Sigplan90 paper] ... After all optimizations were
>applied, programs with bounds checkings [still] ran 0-46% slower than
>programs without bounds checking (down from 78-325% slower). That's a
>pretty large performance degredation ...
Upcoming superscalar architectures offer an opportunity to perform bounds
checking concurrently with other operations. Propagating these checks out
of the critical path of computation (e.g. with techniques such as those
suggested by Gupta) may yield additional safety with little degradation.
It would make a nice change if the next generation of whizbang machines were
not only faster, but "safer" too!
--\-- Jan Prins (email@example.com) "The claim is `always'...
/ Computer Science Dept. ... no, wait, it is `never'..."
--\-- UNC Chapel Hill
Return to the
Search the comp.compilers archives again.