Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!ncar!gatech!mcnc!uvaarpa!murdoch!astsun7.astro.Virginia.EDU!gl8f
From: gl8f@astsun7.astro.Virginia.EDU (Greg Lindahl)
Newsgroups: comp.lang.misc
Subject: Re: Aggressive optimization
Message-ID: <1990Oct18.212844.14728@murdoch.acc.Virginia.EDU>
Date: 18 Oct 90 21:28:44 GMT
References: <13405:Oct1800:22:5690@kramden.acf.nyu.edu> <1493@exodus.Eng.Sun.COM> <20683:Oct1819:44:1490@kramden.acf.nyu.edu>
Sender: news@murdoch.acc.Virginia.EDU
Organization: Department of Astronomy, University of Virginia
Lines: 10

In article <20683:Oct1819:44:1490@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:

>Unsafe transformations and other optimizer bugs. As in sun% cc -O4. Not
>to pick on your compiler, which is otherwise rather nice.

Does Sun's -O4 have bugs, or is that warning in the cc man page
because C programmers leave off "volitile" where it's needed?

--
"Restraint, hell. I'm just too fucking busy." -- Bill Wisner