| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
fixes, cleanups, etc.
not working yet
|
|
|
|
|
|
|
|
|
|
| |
The idea here is to eliminate the set_edgeflags() call in pipe_context
by treating edgeflags as a regular vertex element.
Edgeflags provoke special treatment in hardware, which means we need to
label them in some way, in this case we'll be passing them through the
vertex shader and labelling the vertex shader output with a new TGSI
semantic (TGSI_SEMANTIC_EDGEFLAG).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 unions instead of pointer casts.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
use union instead of casts
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Gets rid of one of the worst strict-aliasing offenders, and actually
produces faster code (at least in some cases, when compiler can use
for instance 64bit moves for memcpy).
(note _mesa_memcpy should get inlined)
|
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
and use it in cubemap instruction sequence for testing
|
| | |
|
| |
| |
| |
| | |
use it in tex cube instruction sequence
|
| |
| |
| |
| | |
looks kinda hackish, should rethink later
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
remember the dst register which is used for cond updates
when it's time to use the cond codes issue a separate PRED instruction
|
| |
| |
| |
| |
| | |
seems assemble_LOGIC was meant for non-condition-code instructions
so execute in for all components as previously
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
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
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
makes testing other things easier - does not hang the card
TODO: enable TEX dependency tracking in vertex programs
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
First time around render targets are not enabled yet (done in
r700SendRenderTargetState) so blend state is not emitted for any targets.
Affects first glClear in some mesa tests.
As a quick fix reorder state emit so that target is set first
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Silences uninitialized variable compiler warning.
|
| | | |
| | | |
| | | |
| | | | |
Also modify the Makefile to use the correct version for the tarballs.
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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 919898e92fa23ff71a59d86a46ff0886a6f34e4d)
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit 364070b1f2b08d43fb205ec198894a35bec6b2f3)
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit 4b0b250aae6ae7d48cd24f9d91d05ab58086c4b2)
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit 76d2ec3a0a047a65ffca70f53848241a3225dad3)
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from commit ea98e9820d7117f7a187f355445796b1ef5d9e0c)
|