Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.misc
Subject: Re: Aggressive optimization
Message-ID: <25336:Oct1823:13:3990@kramden.acf.nyu.edu>
Date: 18 Oct 90 23:13:39 GMT
References: <1493@exodus.Eng.Sun.COM> <20683:Oct1819:44:1490@kramden.acf.nyu.edu> <1990Oct18.212844.14728@murdoch.acc.Virginia.EDU>
Organization: IR
Lines: 11

In article <1990Oct18.212844.14728@murdoch.acc.Virginia.EDU> gl8f@astsun7.astro.Virginia.EDU (Greg Lindahl) writes:
> 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?

Well, the latter can't be the explanation, because their cc doesn't even
understand volatile. Hence the former must be true.

---Dan