Related articles |
---|
strange compiler optimizations qjackson@wave.home.com (Quinn Tyler Jackson) (1998-08-10) |
Re: strange compiler optimizations mtimmerm@microstar.no-spam.com (Matt Timmermans) (1998-08-13) |
Re: strange compiler optimizations clark@quarry.zk3.dec.com (Chris Clark USG) (1998-08-19) |
From: | "Matt Timmermans" <mtimmerm@microstar.no-spam.com> |
Newsgroups: | comp.compilers |
Date: | 13 Aug 1998 22:01:47 -0400 |
Organization: | IGS - Information Gateway Services |
References: | 98-08-042 |
Keywords: | optimize |
Quinn Tyler Jackson wrote in message 98-08-042...
>Why on earth did OPTIMIZE FOR SPEED do so poorly with PLPM and OPTIMIZE FOR
>SIZE do so well, where it behaved as expected for LPM?
Most likely, optimizing for size allowed some important inner loop, and all
the functions it calls, to remain in the cache while executing. This is an
important boundary, because as soon as the loop gets a bit too big, the
whole thing has to be loaded from memory (or the next level of cache) on
each iteration.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.