Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!hubcap!ncrcae!cs-col!almira!haug
From: haug@almira.uucp (Brian R Haug)
Newsgroups: comp.sys.ncr
Subject: Re: Informix 4gl and C optimizer
Message-ID: <1990Dec19.000453.5631@almira.uucp>
Date: 19 Dec 90 00:04:53 GMT
References: <1990Dec14.035146.18882@seachg.uucp>
Reply-To: haug@almira.UUCP (Brian Haug)
Organization: Personal machine, Columbia, SC
Lines: 9

In article <1990Dec14.035146.18882@seachg.uucp> jalsop@seachg.UUCP (John Alsop) writes:
>I'm curious as to why the code generated by Informix' 4GL should cause such
>pathological behaviour of the optimizer.  Ideas anyone?

The reason for this pathological behaviour, taking a wild guess, is that the
code has several constants, and the procedure is fairly long.  At optimization
level 2, one of the optimization run in time proportional to the product of
these two values (length of assembler code and number of constants).  You may
also see this type of behaviour with lex output.