Related articles |
---|
Compiler loop optimizations linuxkaffee@gmx.net (Christian Sturz) (2006-12-29) |
Re: Compiler loop optimizations emailamit@gmail.com (Amit Gupta) (2006-12-31) |
Re: Compiler loop optimizations robert.hundt@gmail.com (Robert H) (2007-01-01) |
Re: Compiler loop optimizations robert.hundt@gmail.com (Robert H) (2007-01-01) |
Re: Compiler loop optimizations torbenm@app-0.diku.dk (2007-01-05) |
Re: Compiler loop optimizations linuxkaffee@gmx.net (Christian Sturz) (2007-01-05) |
Re: Compiler loop optimizations emailamit@gmail.com (Amit Gupta) (2007-01-07) |
Compiler loop optimizations Heiko.Falk@udo.edu (Heiko Falk) (2007-01-10) |
Re: Compiler loop optimizations hebisch@math.uni.wroc.pl (Waldek Hebisch) (2007-01-11) |
Compiler Loop Optimizations plfriko@yahoo.de (Tim Frink) (2008-02-28) |
From: | "Robert H" <robert.hundt@gmail.com> |
Newsgroups: | comp.compilers |
Date: | 1 Jan 2007 11:51:19 -0500 |
Organization: | Compilers Central |
References: | 06-12-10906-12-115 |
Keywords: | optimize |
Posted-Date: | 01 Jan 2007 11:51:19 EST |
Hi Amit,
>>At any rate, for the specified program, a compiler optimization would
>>not result into any endcase significant improvement.
Well, if you can get rid of the control flow in the loop, subsequent
phases (scheduler/pipeliner, etc) might be able to perform a (much)
better job. So, if you can get rid of it, you should definitely try!
Cheers
-- Robert
On Dec 31, 6:25 am, "Amit Gupta" <emaila...@gmail.com> wrote:
> NOW, you don't really need to worry if gcc/CC can optimize this
> particular program. The processor branch prediction unit will be able
> to take care of it. ...
Return to the
comp.compilers page.
Search the
comp.compilers archives again.