| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Tobias Droste <[email protected]>
|
| |
|
|
|
|
| |
We already have lots of GEN6_* defines; this seems more consistent.
|
|
|
|
|
| |
It is pointless to change, now that we don't replace user vertex buffer
with uploaded copy, per commit 52e598d200108ab9cfc9c9d828bbebdc576e9703.
|
|
|
|
|
|
|
|
| |
The code no longer supports otherwise -- it relies on buffers being
uploaded via u_upload_mgr -- so make this clear.
Also, there's no need to flush after draws from user buffers, given all
user content should have been copied by then.
|
|
|
|
|
| |
The years were obtained automatically by scraping the first year from
the spec text file. They are approximate.
|
|
|
|
|
|
|
|
| |
Should prevent the assert failure
svga_buffer_flush_mapped_range: Assertion `sbuf->map.writing' failed.
on nested transfers.
|
| |
|
|
|
|
|
|
|
|
|
| |
Unsigned long is 32bit on several platforms (e.g., Windows), yielding
1UL << 32 to be zero.
Note that BITFIELD64_BIT result is often assigned to variables of type
GLbitfield, instead of GLbitfield64. That's probably wrong and should be
addressed in a later change.
|
| |
|
| |
|
| |
|
|
|
|
| |
This fixes C++ warnings where BITFIELD64_BIT() is used.
|
|
|
|
|
|
|
|
|
|
|
| |
It should have been a tip when the spec says "However, implicitly
sized arrays cannot be assigned to. Note, this is a rare case that
*initializers and assignments appear to have different semantics*."
(empahsis mine)
Fixes bugzilla #34367.
NOTE: This is a candidate for stable release branches.
|
|
|
|
|
|
| |
For mip-map level rendering, both draw offset and size tend to change ...
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
|
|
| |
v2: Make it actually work.
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
|
|
|
|
| |
Early Z support is set in the DST_VARS command. Hence split up static
state emission to avoid reissuing to much on fragment shader changes,
especially the costly dst buffer relocations.
Signed-off-by: Daniel Vetter <[email protected]>
|
|
|
|
|
| |
We were alpha testing against an unwritten value, resulting in garbage.
(part of) Bug #35073.
|
|
|
|
|
|
|
|
| |
The optimization loop won't reinsert noise instructions or quadop
vectors, so we were traversing the tree for nothing. Lowering vector
indexing was in the loop after do_common_optimization() to avoid the
work if it ended up that the index was actually constant, but that has
been called already in the core.
|
|
|
|
| |
It can't call anything, so there's no point.
|
| |
|
|
|
|
| |
It only cares about "if", "loop", and "discard".
|
|
|
|
|
|
| |
Most of the time we don't have a non-uniform struct variable in the
shader, so this cuts the time spent in do_structure_splitting during
glean texCombine by about 2/3.
|
|
|
|
| |
Reduces time spent in this during glean texCombine by about 2/3.
|
|
|
|
| |
Cuts the time spent in this function during glean texCombine by 2/3.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This fixes an issue where the .obj files wound up in the src/
directory rather than the build/ directory. That prevented
combined 32-bit and 64-bit builds from working.
Signed-off-by: Brian Paul <[email protected]>
|
| |
|
| |
|
|
|
|
| |
v2: change the gallium entry point to texture_barrier.
|
| |
|
|
|
|
|
| |
Be sure to type "make clean" after this commit, otherwise your binaries
will segfault.
|
| |
|
|
|
|
|
|
|
|
| |
Additionally, to discarding the whole buffer, use
PIPE_TRANSFER_DISCARD_RANGE in pipe_buffer_write when the
write covers only part of the buffer.
Signed-off-by: Mathias Fröhlich <[email protected]>
|
|
|
|
|
|
|
|
| |
In memory mapping buffer objects make use of
PIPE_TRANSFER_DISCARD_WHOLE_RESOURCE and PIPE_TRANSFER_DISCARD_RANGE
when appropriate.
Signed-off-by: Mathias Fröhlich <[email protected]>
|
| |
|
|
|
|
|
|
| |
Evergreen.
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
|
|
| |
Spotted by Henri on IRC.
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
|
|
|
|
| |
It doesn't support them. Also, we shouldn't be
emitting CB_BLENDx_CONTROL on R600 as the regs don't
exist there, but I'm not sure of the best way to deal
with this in the current r600 winsys.
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
|
| |
Only rv6xx+ support them.
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
|
|
|
| |
This packet is required when updating the DB, CB,
or STRMOUT base addresses on rv6xx for the surface
sync logic to work correctly.
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
|
|
| |
This sort of worked because blend state setup cleared MULTIWRITE_ENABLE again,
but that's not something we want to depend on.
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|