ben@cunixc.cc.columbia.edu (Ben Fried) (06/06/89)
System: VaxStation II running a Van TCP-enhanced Ultrix 2.0 kernel. Sources: X11R3, patchlevel 8, with Purdue 2.0 & 2.1 speedups I just compiled the gcc 1.35 sources, and attempted to make Xqvss, with CC set to: "gcc -fcombine-regs -fstrength-reduce -finline-functions \ -fpcc-struct-return -DPURDUE -Dinline=INLINE -DNOSTDHDRS" I got lots of errors in the ddx/mfb subdirectory - so many that I had to compile it with pcc. The rest of the compile went without incident, but I still couldn't generate an Xqvss binary that actually worked. Has anyone done this before? If so, what am I doing wrong? Or is this a gcc bug manifesting itself? Ben -=-=- ben@columbia.edu ben@cunixc.cc.columbia.edu
grunwald@flute.cs.uiuc.edu (Dirk Grunwald) (06/06/89)
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)
grunwald@flute.cs.uiuc.edu (Dirk Grunwald) (06/06/89)
Whops, I was thinking of the *Xqdss* driver, not Xqvss. I haven't tried Xqdss, since we don't have one. When I did try to compile Xqvss with gcc (about 1.30, I think) it would compile but hang when running because of spin-loops that were to delay while display registers get loaded, etc. -- Dirk Grunwald -- Univ. of Illinois (grunwald@flute.cs.uiuc.edu)