| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It merges FEATURE_ARB_occlusion_query and FEATURE_EXT_timer_query, and
follows the feature conventions.
|
|
|
|
| |
This allows the removal of AEcontext.
|
|
|
|
|
| |
As shown in mfeatures.h, this allows users of texgen.h to work without
knowing if the feature is available.
|
|
|
|
|
| |
As shown in mfeatures.h, this allows users of feedback.h to work without
knowing if the feature is available.
|
|
|
|
|
| |
As shown in mfeatures.h, this allows users of drawpix.h to work
without knowing if the feature is available.
|
|
|
|
|
| |
It is separated from FEATURE_drawpix and made to follow the feature
conventions.
|
|
|
|
|
| |
As shown in mfeatures.h, this allows users of histogram.h to work without
knowing if the feature is available.
|
|
|
|
|
| |
As shown in mfeatures.h, this allows users of attrib.h to work without
knowing if the feature is available.
|
|
|
|
|
| |
As shown in mfeatures.h, this allows users of accum.h to work without
knowing if the feature is available.
|
|
|
|
|
| |
These options can be used to force vertex/fragment shaders to be no-op
shaders (actually, simple pass-through shaders). For debug/test purposes.
|
|
|
|
| |
For debug/test purposes.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
Makefile
configs/default
docs/relnotes.html
src/gallium/drivers/softpipe/sp_context.c
src/gallium/drivers/softpipe/sp_tile_cache.c
src/mesa/main/version.h
|
| | |
|
| |
| |
| |
| | |
See bug 24217.
|
| | |
|
| |
| |
| |
| |
| |
| | |
makes blend functions work better
Signed-off-by: Dave Airlie <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Dave Airlie <[email protected]>
|
| |
| |
| |
| | |
Makes doom3 alot nicer..
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This whole reuse of buffers (TexSubImage instead of TexImage, SubData
instead of Data) is bad for hardware drivers, but it's even worse when
we accidentally try to access the 2x2 PBO to fill the new 16x16 texture
we're creating, producing GL errors.
Fixes piglit pbo-drawpixels. Bug #14163.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
In guess_and_alloc_texture() use the gl_texture_object::GenerateMipmap
field as another hint as to whether to allocate space for a whole mipmap.
|
|\| |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The main issue is we didn't always have a gallium texture object with
enough space to store the to-be-generated mipmap levels. When that's
the case, allocate a new gallium texture and use st_texure_finalize()
to copy images from the old texture to the new one.
We also had the baseLevel parameter to st_render_mipmap() wrong.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't compute the st_texture_object::lastLevel field based on the texture
filters. Use the _MaxLevel value that core Mesa computes for us.
When called from the GenerateMipmap path, we'll use the lastLevel field
as-is.
|
| | |
| | |
| | |
| | | |
Bug #23760 (crashes in wine)
|
| | |
| | |
| | |
| | | |
Avoids an unnecessary fallback.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/mesa/shader/program_parse.tab.c
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
src/mesa/shader/lex.yy.c
src/mesa/shader/program_parse.tab.c
src/mesa/shader/program_parse.tab.h
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conditional write masks and the condition-code based KIL instruction
are all supported. The specific behavior of KIL in the following
shader may or may not match the behavior of other implementations:
!!ARBfp1.0
TEMP GT;
MOVC GT, fragment.texcoord[0];
KIL GT.x;
END
Should be it interpreted as 'KIL srcReg' or as 'KIL ccTest'? The
current parser will interpret it as 'KIL srcReg'.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The lexer will return IDENTIFIER only when the name does not have an
associated symbol. Otherwise USED_IDENTIFIER is returned.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Adds support for declaring TEMP and OUTPUT variables as 'LONG' or
'SHORT' precision. The precision specifiers are parsed, but they are
currently ignored. Some support for this may be added in the future,
but neither Intel hardware nor, as far as I'm aware, Radeon hardware
support multiple precisions.
Also adds support for instruction precision ('X', 'H', and 'R')
suffixes and instruction condition code output ('C') suffix. This
results in a fairly major change to the lexer. Instructions are
matched with all the possible suffix strings. The suffix string are
then carved off by a context (i.e., which program mode and options are
set) aware parser that converts the suffixes to bits in
prog_instruction.
This could have been handled in the same way _SAT was originally
handled in the lexer, but it would have resulted in a very large lexer
with lots of opportunity for cut-and-paste errors.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The new constructor copies fields from the prog_instruction that the
parser expects the lexer to set.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
At this point the extension is not fully implemented.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
ARBfp requires scalar constants have a '.x' suffix, but NVfp_option
does not. This shows up with instructions that require a scalar
parameter (e.g., COS).
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | | |
Conflicts:
src/mesa/drivers/dri/intel/intel_clear.c
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This fixes the clears in openarena with the new metaops clear code, and
the new piglit vbo-subdata-sync test.
Bug #23857.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Its flagging of extra state that's already flagged by the vtbl new_batch
when appropriate was confusing my tracking down of the OA clear bug.
|