🚀 go-pugleaf

>In article <15941@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>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).  

Fine. I don't have the time to deal with it (I work full time, and I'm
a graduate student). Yes, I've looked at the 68000 code with CPR, and
it appears that I can spoof SAS C into generating incorrect offsets for
automatic variables with the optimizor on. I have not noted a particular
pattern of events that lead to this error, other than the optimizor on:
code is incorrect, optimizor off: code is correct.

>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.

Personally, I'm very happy it works for you :-). I'm sick to death of people
saying "It hasn't happened to me, so it must not exist!" It does have bugs.

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

5.10
5.10
5.05
5.10
5.10
5.10
5.05

>Randell Jesup, Keeper of AmigaDos, Commodore Engineering.

--
| ben@epmooch.UUCP   (Ben Mesander)       |
| ben%servalan.UUCP@uokmax.ecn.uoknor.edu |
| !chinet!uokmax!servalan!epmooch!ben     |

SAS bug of the month club:
Open a file that already exists. Now try an access(file,0) call to see
if it exists. It doesn't exist? No? Go look in the directory. Sure 'nuff,
it's there. Looks to me like someone said: "Lock() failed? Doesn't exist!"
without checking the return value to see if the "object was in use".