Re: Loop Optimizations and Gotos

preston@tera.com (Preston Briggs)
Tue, 21 Nov 1995 06:37:35 GMT

          From comp.compilers

Related articles
[4 earlier articles]
Re: Loop Optimizations and Gotos cdg@nullstone.com (1995-11-13)
Re: Loop Optimizations and Gotos faiman@zko.dec.com (1995-11-16)
Re: Loop Optimizations and Gotos hrubin@stat.purdue.edu (1995-11-17)
Re: Loop Optimizations and Gotos j-grout@glibm9.cen.uiuc.edu (1995-11-17)
Re: Loop Optimizations and Gotos baynes@ukpsshp1.serigate.philips.nl (1995-11-20)
Re: Loop Optimizations and Gotos plong@perf.com (Paul Long) (1995-11-21)
Re: Loop Optimizations and Gotos preston@tera.com (1995-11-21)
Re: Loop Optimizations and Gotos cliffc@ami.sps.mot.com (1995-11-21)
Re: Loop Optimizations and Gotos cliffc@ami.sps.mot.com (1995-11-22)
Re: Loop Optimizations and Gotos Paul_Long@ortel.org (1995-11-23)
Re: Loop Optimizations and Gotos bill@amber.ssd.hcsc.com (1995-11-27)
Re: Loop Optimizations and Gotos dave@occl-cam.demon.co.uk (Dave Lloyd) (1995-11-27)
Re: Loop Optimizations and Gotos hrubin@stat.purdue.edu (1995-11-29)
| List of all articles for this month |
Newsgroups: comp.compilers
From: preston@tera.com (Preston Briggs)
Keywords: C, optimize
Organization: Compilers Central
References: 95-11-076 95-11-107 95-11-158
Date: Tue, 21 Nov 1995 06:37:35 GMT

>Dave Lloyd <dave@occl-cam.demon.co.uk> wrote:
>>It's simple - don't use goto. Many compilers have extra levels of
>>optimisation that only kick in when a control construct can be
>>clearly recognised that are not feasible in general for gotos.


and hrubin@stat.purdue.edu (Herman Rubin) writes:
>I suggest then that the fault is in the compiler writers.


and the moderator wrote:


>Herman's opinions on the merits of gotos have been argued at length
>before and I'd rather not rehash the arguments here again.


Nevertheless, I agree with Rubin in this case. If a compiler doesn't
recognize a loop built out of if's and goto's, the compiler writer was
a little lazy.


On the other hand, for portable performance across a range of
compilers, perhaps it's better to be conservative. Or simply test the
compiler before you pay for it.


Preston Briggs
--


Post a followup to this message

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