| Age | Commit message (Collapse) | Author |
|---|
|
This is a follow-up to commit b85c71d4e1e4ed788be834dff5b7b3c0cd0402ac
which added u_staging.c to make.
|
|
|
|
|
|
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
|
|
Should fix few glBitmap cases.
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
|
|
Thanks to Michal for spotting this.
|
|
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
|
|
supported"
This reverts commit 16b45ca7cefb3432b4133fe9d0b1dbfe3f286131.
José Fonseca asked for a revert.
Note that the testsuite will now segfault since it attempts to test
all possible formats.
|
|
translate was attempting to output A8R8G8B8_UNORM as if it were
R8G8B8A8_UNORM.
Now the tests just added pass.
|
|
Currently only checks all possible format conversions, and doesn't
attempt to test whether multiple buffers/elements or indices work.
|
|
This gives the caller a chance to recover (or crash anyway otherwise).
|
|
util_framebuffer_copy was attempting to copy all elements of the
source framebuffer state.
However, this breaks if the user does not zero initialize the structure.
Instead, only copy the elements up to nr_cbufs, and clear elements up
to dst->nr_cbufs, if the destination was larger than the source.
|
|
Single divide, so let lp_build_div decide how to implement this.
This will save a multiplication in architectures which don't have
a RCP intrinsic.
|
|
Texture dimensions are unsigned.
|
|
|
|
|
|
|
|
Direct3D 10/11 has no concept of transfers. Applications instead
create resources with a STAGING or DYNAMIC usage, copy between them
and the real resource and use Map to map the STAGING/DYNAMIC resource.
This util module allows to implement Gallium drivers as a Direct3D
driver would be implemented: transfers allocate a resource with
PIPE_USAGE_STAGING, and copy the data between it and the real resource
with resource_copy_region.
|
|
Used when we want to be sure the compiler inlines a large function into
an inner loop.
|
|
Used to find out if a surface exists without creating one.
|
|
Using cso_hash directly is the right thing since util_hash_table
adds useless overhead and is harder to use for this application.
|
|
|
|
They are unimplemented, even though the framework makes it possible to
implement them well, and nv50 needs them.
|
|
Current practice is to start identifiers with "util_" instead of "u_".
|
|
This is a simple framework that handles splitting primitives in an
abstract way.
The user has to specify the primitive start, start index and count.
Then, it can ask the primitive splitter to "draw" a chunk of the
primitive, staying under a given vertex/index budget.
The primitive splitter will then call user-supplied functions to
emit a range of vertices/indices, as well as switch the edgeflag
on or off.
This is particularly useful for hardware that either has limits
on the vertex count field, or where vertices are pushed on a FIFO
or temporary buffer of limited size.
Note that unlike other splitters, it does not manipulate data in
any way, and merely asks a callback to do so, in vertex intervals.
|
|
Include glheader.h for GLfloat symbol.
|
|
Remove mfeatures.h.
Include glheader.h for GL symbols.
|
|
Include mtypes.h for GLcontext symbol.
|
|
Include mtypes.h for GLcontext symbol.
|
|
Include mtypes.h for GLcontext symbol.
|
|
Include mtypes.h for GLcontext symbol.
|
|
|
|
See fd.o bug 29487.
NOTE: This is a candidate for the 7.8 branch.
Signed-off-by: Brian Paul <brianp@vmware.com>
|
|
This got lost during the rasterizer rewrite.
|
|
|
|
|
|
|
|
We're already using the return-value of cmp to print either PASS or
FAIL and in the case of failure, we're subsequently running and
showing the output of diff. So any warnings/errors from cmp itself are
not actually needed, and can be quite confusing.
|
|
Commit d4a04f315560704bf1103df0b93723e468725df7 caused this test case
to produce an additional blank line, which is otherwise harmless, but
does need to be reflected in the .expected file for the test to pass.
|
|
|
|
|
|
|
|
After making a minor change to the .y file.
|
|
Since we have a custom structure for YYLTYPE locations, we need to use
an %initial-action directive to avoid triggering use of uninitialized
memory when, for example, printing error messages.
We apparently don't yet have a test case that allowed valgrind to find
this bug for us, but valgrind found a similar problem in the other
parser, so we fix this one as well.
|
|
After making a minor change to the .y file.
|
|
Since we have a custom structure for YYLTYPE locations, we need to use
an %initial-action directive to avoid triggering use of uninitialized
memory when, for example, printing error messages.
Thanks to valgrind for noticing this bug.
|
|
Signed-off-by: Brian Paul <brianp@vmware.com>
|
|
|
|
|
|
|
