On Mon, 2011-02-14 at 11:04 -0800, Marek Olšák wrote:
> On Mon, Feb 14, 2011 at 6:58 PM, José Fonseca
> mailto:jfons...@vmware.com>> wrote:
> Marek,
>
> I'm OK with removing pipe_vertex_buffer::max_index but there is a bit
> more work involved, as they are not really equivalent in the guarantees.
On Mon, Feb 14, 2011 at 6:58 PM, José Fonseca wrote:
> Marek,
>
> I'm OK with removing pipe_vertex_buffer::max_index but there is a bit
> more work involved, as they are not really equivalent in the guarantees.
>
> pipe_vertex_buffer::max_index is an attribute of the vertex buffer -- it
> describ
Marek,
I'm OK with removing pipe_vertex_buffer::max_index but there is a bit
more work involved, as they are not really equivalent in the guarantees.
pipe_vertex_buffer::max_index is an attribute of the vertex buffer -- it
describe the max index that can be fetch from the buffer without running
i
This is redundant to pipe_draw_info::max_index and doesn't really fit
in the optimizations I plan.
---
src/gallium/auxiliary/draw/draw_llvm.c | 17 -
src/gallium/auxiliary/draw/draw_llvm.h |5 +
src/gallium/auxiliary/draw/draw_pt.c |
