Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!ncar!ames!ll-xn!mit-eddie!uw-beaver!apollo!mrst!sdti!mjy
From: mjy@sdti.UUCP (Michael J. Young)
Newsgroups: comp.unix.microport
Subject: Re: Optomizer (used to be: nethack on uport sys V)
Message-ID: <270@sdti.UUCP>
Date: 23 May 88 13:44:00 GMT
References: <229@eutrc3.UUCP> <1640@hubcap.UUCP> <400@smegma.UUCP>
Reply-To: mjy@sdti.UUCP (0000-Michael J. Young)
Organization: Software Development Technologies, Sudbury MA
Lines: 16

In article <400@smegma.UUCP> mdg@smegma.UUCP (Marc de Groot) writes:
>Just a quick note that down at Microport, we compile the entire kernel
>with the optimizer turned on and don't have any problems. That's not to
>say they don't exist, but we have had good success with the optimizer.

Gee, maybe now we know the source of dual-drive disk I/O errors!  :-)

Seriously, though, either that optimizer doesn't do anything useful, or
you will eventually run into problems with the driver code.  Most of
the discussion in comp.lang.c about use of 'volatile' should make it
clear why optimizers and device drivers don't mix well.
-- 
Mike Young - Software Development Technologies, Inc., Sudbury MA 01776
UUCP     : {decvax,harvard,linus,mit-eddie}!necntc!necis!mrst!sdti!mjy
Internet : mjy%sdti.uucp@harvard.harvard.edu      Tel: +1 617 443 5779
"Bill & Opus in '88" -- Consider the alternatives!