Re: Loop jamming!?

"Steve Simmons" <simmons@nortel.ca>
29 Jul 1997 13:56:37 -0400

          From comp.compilers

Related articles
[4 earlier articles]
Re: Loop jamming!? n8tm@aol.com (1997-07-16)
Re: Loop jamming!? cdg@nullstone.com (Christopher Glaeser) (1997-07-18)
Re: Loop jamming!? schow@nortel.ca (Stanley Chow) (1997-07-21)
Re: Loop jamming!? cdg@nullstone.com (Christopher Glaeser) (1997-07-22)
Re: Loop jamming!? n8tm@aol.com (1997-07-27)
Re: Loop jamming!? genew@netcom.com (1997-07-28)
Re: Loop jamming!? simmons@nortel.ca (Steve Simmons) (1997-07-29)
Re: Loop jamming!? schow@nortel.ca (Stanley Chow) (1997-07-31)
Re: Loop jamming!? jan@fsnif.neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) (1997-07-31)
Re: Loop jamming!? cliff.click@Eng.Sun.COM (cliffc) (1997-08-07)
Re: Loop jamming!? mkent@acm.org (Mike Kent) (1997-08-07)
Re: Loop jamming!? schow@nortel.ca (Stanley Chow) (1997-08-09)
| List of all articles for this month |

From: "Steve Simmons" <simmons@nortel.ca>
Newsgroups: comp.compilers
Date: 29 Jul 1997 13:56:37 -0400
Organization: Nortel
References: 97-07-089 97-07-102 97-07-108
Keywords: optimize, architecture

> I understood "In the extreme case, the slower loop is not slowed down"
> to mean there are *no* programs that will slow as a result of loop
> jamming. I contend such programs *do* exist. These two assertions can
> not both be true. Either such programs exist, or they do not.




Every compiler optimization performed has a risk of producing slower
code. A good compiler can catch many of these instances by analysis
before the transformation; however, no compiler can catch all of
these instances.


Usually, a rule of thumb is to perform the transformation if
it results in a performance enhancement a majority of the time,
and the downside risk is minimal.


Loop jamming/fusion increases the number of generated instructions,
and can thus introduce page faulting in the body of the loop where no page
fault existed before. Obviously, this would slow down your code.


--


Post a followup to this message

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