Re: array index checking optimizations?

tmb@best.com (Thomas Breuel)
5 May 1996 17:49:53 -0400

          From comp.compilers

Related articles
[5 earlier articles]
Re: array index checking optimizations? markt@harlequin.co.uk (1996-05-01)
array index checking optimizations? dave@occl-cam.demon.co.uk (Dave Lloyd) (1996-05-02)
Re: array index checking optimizations? mad@math.keio.ac.jp (1996-05-03)
Re: array index checking optimizations? prener@watson.ibm.com (1996-05-03)
Re: array index checking optimizations? ben@sys.toronto.edu (1996-05-03)
Re: array index checking optimizations? dlmoore@ix.netcom.com (1996-05-03)
Re: array index checking optimizations? tmb@best.com (1996-05-05)
Re: array index checking optimizations? Patrick.Cousot@ens.fr (Patrick Cousot) (1996-05-08)
| List of all articles for this month |

From: tmb@best.com (Thomas Breuel)
Newsgroups: comp.compilers
Date: 5 May 1996 17:49:53 -0400
Organization: home
References: 96-04-140 96-05-032
Keywords: optimize

ben@sys.toronto.edu (Benjamin Gamsa) writes:


      Is it safe to assume that many (most?) compilers will at the least,
      reduce checking to loop entry code to verify certain constraints
      and/or have multiple versions of a loop depending on run-time values?


Only a few high compilers for high-performance applications will do
that. In fact, compiling multiple versions isn't a win most of the
time, since you usually don't want to pay the memory cost.


Actually, the best way of handling such situations is via on-they-fly
compilation and optimization, when runtime information about hotspots,
types, and bounds is available. Maybe the current flurry of activity
in building JIT compilers for Java will finally make this kind of
technology mainstream.


Cheers,
Thomas.
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.