Xref: utzoo gnu.gcc.bug:1192 comp.windows.x:10628 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!uxc!garcon!garcon.cso.uiuc.edu!grunwald From: grunwald@flute.cs.uiuc.edu (Dirk Grunwald) Newsgroups: gnu.gcc.bug,comp.windows.x Subject: Re: Building XQvss with GCC 1.35? Message-ID: Date: 6 Jun 89 15:23:05 GMT References: <1567@cunixc.cc.columbia.edu> Sender: news@garcon.cso.uiuc.edu Reply-To: grunwald@flute.cs.uiuc.edu Organization: University of Illinois, Urbana-Champaign Lines: 8 In-reply-to: ben@cunixc.cc.columbia.edu's message of 5 Jun 89 23:12:01 GMT this is, I think, an Xqvss bug, not a gcc bug. whoever cobbled together the Xqvss driver made unsafe assumptions about the optimizer - in particular, you have to compile everything with -fvolatile & even then I'm not certain it will work properly. -- Dirk Grunwald -- Univ. of Illinois (grunwald@flute.cs.uiuc.edu)