Related articles |
---|
[5 earlier articles] |
Re: eliminating array bounds checking overhead Sid-Ahmed-Ali.TOUATI@inria.fr (Sid Ahmed Ali TOUATI) (2000-04-27) |
Re: eliminating array bounds checking overhead rhyde@shoe-size.com (Randall Hyde) (2000-04-27) |
Re: eliminating array bounds checking overhead nr@labrador.eecs.harvard.edu (2000-04-27) |
Re: eliminating array bounds checking overhead terryg@uswest.net (Terry Greyzck) (2000-04-27) |
Re: eliminating array bounds checking overhead fjscipio@rochester.rr.com (Fred J. Scipione) (2000-04-27) |
Re: eliminating array bounds checking overhead sandeep@ddi.com (Sandeep Dutta) (2000-04-29) |
Re: eliminating array bounds checking overhead tej@melbpc.org.au (Tim Josling) (2000-04-30) |
Re: eliminating array bounds checking overhead markw65@my-deja.com (Mark Williams) (2000-04-30) |
Re: eliminating array bounds checking overhead d95josef@dtek.chalmers.se (2000-04-30) |
Re: eliminating array bounds checking overhead mayur_naik@my-deja.com (2000-04-30) |
Re: eliminating array bounds checking overhead terryg@uswest.net (Terry Greyzck) (2000-05-01) |
Re: eliminating array bounds checking overhead monnier+comp/compilers/news/@flint.cs.yale.edu (Stefan Monnier) (2000-05-01) |
Re: eliminating array bounds checking overhead r_c_chapman@my-deja.com (2000-05-01) |
[5 later articles] |
From: | Tim Josling <tej@melbpc.org.au> |
Newsgroups: | comp.compilers |
Date: | 30 Apr 2000 00:14:31 -0400 |
Organization: | Melbourne PC User Group |
References: | 00-04-194 00-04-209 |
Keywords: | optimize, bibliography |
IBM has published some material their Java implementation - how
they eliminate the checks in many cases. Often you can break a
loop up into subranges where only some subranges require explicit
checking. I can't remember where it was - maybe in IEEE Software.
The GCC compiler is having smart pointers added to it, and they
are working on optimising the boudns checks aways when possible.
Tim Josling
[Midkiff, Moreira, and Snir, "Optimizing array reference checking in
Java Programs", IBM Systems Journal 37:3, 1998, pp. 409-453. Nothing
exotic, hoisting bounds checks out of do loops, breaking the loops
into subranges to get invariants they can optimize, but the results
show that it's very effective. The entire issus 39:1 is on Java
Performance, they have an article in there too but it doesn't say
anything more about bounds checking. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.