Xref: utzoo comp.unix.sysv386:8474 comp.lang.c:39641
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!spool.mu.edu!munnari.oz.au!goanna!ok
From: ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe)
Newsgroups: comp.unix.sysv386,comp.lang.c
Subject: What's HCR-PCO?
Message-ID: <6000@goanna.cs.rmit.oz.au>
Date: 28 May 91 07:09:26 GMT
References: <381@tmcsys.UUCP> <1991May22.130713.25852@sco.COM> <1991May27.134736.6450@sco.COM>
Followup-To: comp.lang.c
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 11

In article <1991May27.134736.6450@sco.COM>, david@sco.COM (David Fiander) writes:
> Most of the bugs reported against
> HCR-PCO (the Portable Code Optimizer) turned out to be bugs in the
> application source which worked until an agressive optimizer hacked the
> code into something else.

What's HCR-PCO?  Sounds interesting.
-- 
Should you ever intend to dull the wits of a young man and to
incapacitate his brains for any kind of thought whatever, then
you cannot do better than give him Hegel to read.  -- Schopenhauer.