On Tue, Jun 29, 2004 at 08:35:53PM +0800, [EMAIL PROTECTED] wrote:
If I don't use gcc -O2 flag to compile dri driver,quake3 can run
smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until the
menu
comes up.
Umm,
On Mer, 2004-06-30 at 13:45, [EMAIL PROTECTED] wrote:
I am developing the DRI driver for s3 latest product DeltaChrome.
XFree86 version is 4.3.0,and gcc is the default in redhat9.0,
and the output of gcc -v is:
cc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Furthermore,if I enable -O2
If I don't use gcc -O2 flag to compile dri driver,quake3 can run smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until the menu
comes up.
If some variables should be protected by volatile,such as mmio address,
DMA buffer?
If I don't use gcc -O2 flag to compile dri driver,quake3 can run smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until the menu
comes up.
Umm, could you tell us what version of gcc you are using? If you
are using the
If I don't use gcc -O2 flag to compile dri driver,quake3 can run smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until the menu
comes up.
also details of graphics card, source tree you are building from ..
Dave.
On Tue, Jun 29, 2004 at 09:56:56PM +0800, Dave Airlie wrote:
If I don't use gcc -O2 flag to compile dri driver,quake3 can run
smoothly.
But when I enable -O2 flag,the driver is broke.
Quake3 always displays the last frame of the last q3 startup until
the menu
comes up.
also
