🚀 go-pugleaf

In article <ben.3508@epmooch.UUCP> ben@epmooch.UUCP (Rev. Ben A. Mesander) writes:
>>In article <15941@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>>	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.

Wow!  I don't think Randell was suggesting that the problem you were
having didn't exist, just that it might have been fixed.  You say you
don't have time to deal with it, but you apparently have time to let us
all know how much trouble everything is for you.  Randell was trying to
help you with your problem.  It appears that you really don't want help,
you just want to complain.

I'll bet the whole net is "sick to death" of people saying this or that
is junk or broken, when they won't take appropriate steps to take care
of it, except to tell everyone on the net how clever they were to find a
bug.

The point I think you're missing in all of this is that it doesn't do
anyone any good for you to tell us that SAS/C is broken, or a lousy
compiler, or even that GCC is better, if you're not willing to report
the problems/bugs to the proper people.  Usenet isn't SAS/C support.

>| ben@epmooch.UUCP   (Ben Mesander)       |
>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".

Have you reported it?

(*Sigh*)
-hans
------------------------------------------------------------------------
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO