Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: '386 XENIX "cc -Ox" optimization bug
Keywords: -Ox
Message-ID: <2548@sixhub.UUCP>
Date: 9 Dec 90 15:59:43 GMT
References: <40991@ut-emx.uucp>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 12

In article <40991@ut-emx.uucp> jon@ccwf.cc.utexas.edu (Jon Boede) writes:

| It's a little bothersome to turn on "max. optimization" and have your code stop
| working! ;-)

  My manual calls this "unsafe optimization" or some such. Besides, you
get the wrong answer, but much faster!  ;-)
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me