🚀 go-pugleaf

According to al@unhd.unh.edu.UUCP (Anthony Lapadula):
>In article <265861D7.3293@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes:
>>Because aliasing is such a basic feature of the language, it is not
>>fair to clue in the compiler: "Psst!  This is one of those special
>>programs that doesn't do aliasing.  Unholster the benchmark gun."
>
>I suppose we should just give up helpful optimizations until
>the compiler is smart enough to figure out when aliasing isn't present?

Use whatever optimization you like for personal code.  My only
complaint is about the use of a C-subset compiler ("cc -Oa") to
compile published benchmark programs that are misrepresented as C
compiler benchmarks.

>Hmmmm.  How do you feel about "register"?  Is that cheating?

Nope.  It's a part of standard C.

>Just to add in my 2 cents, within the past year I've completed 2
>medium-sized programs (each ~10,000 lines) using MSC 5.1.
>I was quite please (surprised?  not quite) that the -Ox did *not*
>break a single line of code.

That's nice.  It's also irrelevant.  Just because other people
restrict themselves to a C subset does not make Microsoft right for
publishing C-subset benchmarks misrepresented as C benchmarks.
-- 
Chip Salzenberg at ComDev/TCT   <chip%tct@ateng.com>, <uunet!ateng!tct!chip>