| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The util_format_layout name was unfortunate and there
are as been a lot of confusion due to this. Hopefully
this will shed some light on what it was meant for.
Bottom line is: do not rely on these values unless
you're automatically code generating pixel
packing/unpacking routines.
Suggestions for better names than util_format_layout
are welcome!
|
| |
|
| |
|
|
|
|
| |
all code in gallium should use boolean not bool
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In particular, gcc man page warns that
union a_union {
int i;
double d;
};
int f() {
double d = 3.0;
return ((union a_union *) &d)->i;
}
"might" not be ok (why not?), even though it doesn't seem to generate
any warnings. Hence don't use this and do the extra step to actually use
assignment to get the values in/out of the union.
This changes parts of 3456f9149b3009fcfce80054759d05883d3c4ee5.
|
| |
| |
| |
| |
| |
| |
| |
| | |
use pointer to union instead of void pointer.
gcc complained a lot, depending what the pointer originally actually was.
Looks like it's in fact maybe legal to cast for instance uint pointers to
union pointers as long as union contains a uint type, hence use this with some
callers, other just use union util_color in the first place.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This was discovered by the pipe_reference api change.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Historically, parts of mesa code are not strict-aliasing safe, hence
-fno-strict-aliasing is needed to compile (this got forgotten for scons
builds for gallium, which indeed not only caused compiler warnings but also
unexplicable crashes in non-debug builds). However, we should try to eliminate
code not complying with strict-aliasing code at least for gallium.
Hence change pipe_reference functions to make them strict-aliasing compliant.
This adds a bit more complexity (especially for derived classes) but is the
right thing to do, and it does in fact fix a segfault.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The ureg and/or tgsi-simplification work introduced some inconsistencies
between the ureg and traditional TGSI construction code.
Now the tgsi_instruction::NrTokens field is consistant and the
tgsi_header::BodySize field isn't off by one.
Fixes bug 25455.
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Not sure how vmw_screen.c could build at all though...
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/mesa/drivers/dri/r600/r700_assembler.c
src/mesa/main/version.h
|
| |\ \ |
|
| | | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
progs/demos/projtex.c
progs/xdemos/glxinfo.c
src/mesa/main/version.h
To fix the confilicts in projtex.c and glxinfo.c I just took the code from
mesa_7_6_branch. The conflicts seem to have occured from cherry-picks from
mesa_7_7_branch to mesa_7_6_branch followed by commmits just to
mesa_7_6_branch.
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit 052b127842af3372fd768eae8e29b240a696a12a)
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit ea98e9820d7117f7a187f355445796b1ef5d9e0c)
|
| | | |
| | | |
| | | |
| | | | |
Fixes bug 24501
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit 36e2074b63e3e5bc489eb74cad0cd97eafcedb40)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Well, technically non-r[345]xx. At any rate...
$ glxgears
libGL: OpenDriver: trying /home/simpson/mesa/lib/gallium/r600_dri.so
131 frames in 5.0 seconds = 26.107 FPS
I'm sure you can see where this is going. :3
|
| | | |
| | | |
| | | |
| | | | |
Allows us to finally remove radeon_winsys_softpipe.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If *I* can't read it, there's a strong possibility others can't,
either.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Thanks to Bob Gleitsmann for the patch.
I'll clean this up in a better way later if noone else beats me to it.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Otherwise a CS is refused by kernel 2.6.31 (and maybe all later
versions, not sure).
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Just make it cover the whole framebuffer in that case. Otherwise the kernel CS
checker may complain, e.g. running progs/demos/gearbox. That runs fast now
here, but doesn't look right yet.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
The dump calls should be wrapped in #ifdef DEBUG .. #endif.
|
| | | |
| | | |
| | | |
| | | | |
Helps verifying udis86 output.
|
| | | |
| | | |
| | | |
| | | | |
Otherwise the terminal gets full of garbage.
|
| | | |
| | | |
| | | |
| | | | |
Just enough boilerplate code to avoid segfaulting.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This shouldn't happen but it does by some misterious reason. Fail the
assertion but at least do not segfault on release builds.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Apparently not only unnecessary but also causes gcc to complain.
|
| | | |
| | | |
| | | |
| | | | |
Also, overlapping occlusion queries seems to work now.
|
| | | | |
|