| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Although for GL a zero stride means tightly packed elements, Mesa
internally uses zero strides for constant arrays.
Therefore user buffers need to be defined from
buffer_offset + src_offset + min_index*stride
to
buffer_offset + src_offset + max_index*stride + elem_size
Simplifying the later with (max_index + 1)*stride will give zero
sized buffers.
This change also aggregates the st_context's info about user buffers
into a single array.
|
| |
|
|
|
|
|
|
|
|
| |
We adjust 'end' to fit into _MaxElement, but that may result into a 'start'
value bigger than 'end' being passed downstream, causing havoc.
This could be seen with arb_robustness_draw-vbo-bounds, due to an
application bug.
|
|
|
|
|
|
|
|
| |
order.
Simply port the same logic from setup_interleaved_attribs().
Avoids overflow in mustpass.c and feedback.c conform tests.
|
|
|
|
| |
Signed-off-by: Zou Nan hai <[email protected]>
|
|
|
|
| |
Reviewed-by: Brian Paul <[email protected]>
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit b0866f6cfdfcaf23686b1ae2a99627d468196db2)
|
| |
|
|
|
|
|
|
| |
This fixes piglit fbo/fbo-drawbuffers-blend-add.
Signed-off-by: Henri Verbeet <[email protected]>
|
| |
|
|
|
|
| |
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=36032
|
|
|
|
| |
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=36033
|
|
|
|
| |
Note: This is a candidate for the 7.10 branch.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Observe the actual type hierarchy and polymorphism of sampler views and
surface state.
s/texture/resource/
etc.
|
|
|
|
|
|
|
| |
This reverts commit dcdf94c87c087186f963b6e201b2989c61a76ef0.
No retrace support anymore, so human-legible representation of blend
state is much more useful than a blob.
|
|
|
|
|
|
|
|
|
| |
Because:
- bindings are not fully automatic, and they are broken most of the time
- unit tests/samples can be written in C on top of graw
- tracing/retracing is more useful at API levels with stable ABIs such as
GL, producing traces that cover more layers of the driver stack and and
can be used for regression testing
|
| |
|
|
|
|
| |
No GLSL or driver support yet.
|
| |
|
| |
|
|
|
|
| |
Fixes MinGW SCons build.
|
|
|
|
|
|
| |
src_reg already used this; make dst_reg use it too.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
|
| |
Rename ir_to_mesa_undef to undef_src, for clarity.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
|
| |
Makes the code just a little bit cleaner.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
|
|
|
| |
There's really no need for a prefix on member functions, and overloading
takes care of the _op1/_op2 distinction quite nicely. Eric already made
a similar change in the i965 FS backend.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than ir_to_mesa_dst_reg_from_src and ir_to_mesa_src_reg_from_dst.
The new constructors are marked 'explicit' so that the compiler can
catch cases where source and destination registers were accidentally
interchanged.
This also necessitated using constructors to initialize the undef and
address registers, as well as adding a default constructor.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
Both classes are completely private to ir_to_mesa.cpp, so there won't be
any name conflicts with other parts of Mesa. The prefix simply makes it
harder to read.
Also, use a class rather than typedef structs.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
|
|
| |
This is in preparation from removing the "ir_to_mesa_" prefix on the
src_reg and dst_reg types, which would cause a naming conflict.
Reviewed-by: Ian Romanick <[email protected]>
|
|
|
|
|
| |
My feeble attempt to invoke the extract_git_sha1 script from
SConscript didn't work. Hopefully this will do for now.
|
|
|
|
|
|
| |
Reviewed-by: Corbin Simpson <[email protected]>
Reviewed-by: Kristian Høgsberg <[email protected]>
Tested-by: Sedat Dilek <[email protected]>
|
|
|
|
|
|
| |
Reviewed-by: Corbin Simpson <[email protected]>
Reviewed-by: Brian Paul <[email protected]>
Tested-by: Sedat Dilek <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code would previously handle the projection, then swizzle the
shadow comparitor into place. However, when the projection is done
"by hand," as in the TXB case, the unprojected shadow comparitor would
over-write the projected shadow comparitor.
Shadow comparison with projection and LOD is an extremely rare case in
real application code, so it shouldn't matter that we don't handle
that case with the greatest efficiency.
NOTE: This is a candidate for the stable branches.
Reviewed-by: Brian Paul <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=32395
|
| |
|
|
|
|
| |
NOTE: This is a candidate for the 7.9 and 7.10 branches.
|
|
|
|
| |
Signed-off-by: Brian Paul <[email protected]>
|
|
|
|
| |
Signed-off-by: Brian Paul <[email protected]>
|
|
|
|
| |
Silences constant overflow compiler warning.
|