30 Mar 96 04:14, david nugent wrote to andrew clarke:

 ac>> QC has an optimiser, albeit not a particularly configurable one.

 > Perhaps you forgot the quotes around the word "optimiser".

Noted.  :-)

 > It does an abysmal job, and you'll often get better code from
 > leaving it off. The one in QC is *not* the same one as in MSC (nor

Ok, I don't use QC much, although it (the compiler, not necessarily the
code it generates) does live up to its name being relatively quick compared
to the other compilers I use.  I've never used MSC.  Generating bound
16-bit applications would be handy though.

 ac>> Unfortunately there doesn't seem to be a way (eg. a pragma) to
 ac>> tell the QC compiler that the function should return whatever
 ac>> value happens to be in AX; the compiler will always report a "No

 ac>> I could always disable all warnings, but that's somewhat less
 ac>> than useful.

 > Or simply create a variable on the stack. and move your return
 > value there and return it.

Yeah, seems like the only solution.  Seems a bit wasteful though.  :-)

--- Msgedsq/2 3.30