🚀 go-pugleaf

In article <ben.3496@epmooch.UUCP> ben@epmooch.UUCP (Rev. Ben A. Mesander) writes:
>Examples of non-trivial programs that are broken when you use the SAS
>optimizer:
>
>MicroEMACS
>egrep
>sed
>awk
>teco
>GNU chess
>pdtar

	Have you bothered figuring out why those programs broke?  Most things
I've seen 'broken' by the optimizer was code that was already buggy but
happened to work because the compiler wasn't as agressive, or because of
side-effects.  There may be optimizer bugs, but if there are you should
report them (SAS is very good about fixing bugs if given an example).  
Personally, I always use the optimizer, and have yet to hit a bug in it
personally.  There were some lc2 bugs (in some betas) that only showed up
if the optimizer was on - perhaps this is some of what you're seeing.

	Lastly, which version are you using (when you last tried those)?

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
Thus spake the Master Ninjei: "If your application does not run correctly,
do not blame the operating system."  (From "The Zen of Programming")  ;-)