Age | Commit message (Collapse) | Author |
|
This determines if points should be rasterized according to GL point rules
or as normal quads (GL point sprites / d3d points / d3d point sprites).
|
|
there was some confusion between point size state and point size output.
|
|
|
|
Don't need sprite coord origin per coord.
Also, don't need separate sprite enable bit - if all coords have it diabled,
then there are no point sprites (technically, there's a distinction in pre-GL3,
but it only differs in having more leniency in clamping to max size, something
the state tracker would need to handle and the hardware won't bother anyway).
Also, use packed field for the per-coord enables.
All in all, should save 3 dwords in rasterizer state (from 10 down to 7).
|
|
The state tracker is responsible for clamping to any graphics API enforced
size min/max limits for both the static point_size setting as well as per
vertex point size (in the vertex shader).
Note that mesa state tracker didn't actually use these values.
|
|
Mark all functions start with glX as public.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
These functions are the API of Gallium state tracker, and are used by
EGL.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
As the default build has -fvisibility=hidden, add a macro to control the
visibility.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
Temporary. We should soon have the ability to integrate with any driver
via glx extensions.
|
|
As displaying surfaces directly isn't supported by the python state
tracker.
|
|
|
|
As the python state tracker is not integrated with window system an
cannot present surfaces directly.
|
|
It was bugging me. +1 FPS on softpipe.
|
|
|
|
|
|
If somebody goes through that much effort, they probably intended it.
So humor them. :3
|
|
copypix works just fine.
|
|
the xorg state tracker really wants the driver to handle overlapping
blits, and r300 uses u_blitter for blits. This patch adds overlapping
blit support via a temporary surface when its required.
|
|
Argfl. Some of this code is so questionable.
|
|
|
|
Goddammit, some of these hax are really annoying.
|
|
According to the docs, this decreases stalls, and indeed we get a tiny
bit more glxgears from it.
|
|
Simplify the code. Added a comment to keep me from doing it again.
|
|
I want to stab things now.
|
|
|
|
Fixes gnome-shell on nouveau, as well as window resize with various
other applications.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
|
|
Also do state-change checks. ZTOP's too important to not check.
|
|
Also a bit of ztop.
|
|
Meh.
|
|
|
|
No benefits yet.
|
|
Explain how to build for windows. Both MSVC 9 and cross MinGW supported.
Stop documenting LLVM 2.5 as supported. It still supported at the moment
but it will soon stop being.
|
|
The call to _eglSwapBuffers is unnecessary, and the function is missing
when -fvisibility=hidden. Also remove the extraneous braces and indent
the block.
|
|
debug builds.
|
|
|
|
ad-hoc definitions.
Everybody is using the C99's integer types. Everybody except Microsoft,
which in turns means everybody is including their own definitions of C99
integer types for MSVC, causing duplicate definitions when linking two
projects. This is the case of building Gallium and LLVM with MSVC.
Shipping alternative stdint.h and stdbool.h headers for MSVC allows us
to share a single definition. It also removes clutter from the Gallium
headers.
|
|
|
|
|
|
|
|
Conflicts:
src/mesa/drivers/dri/i965/brw_wm_emit.c
|
|
|
|
|
|
Hopefully adddresses fdo 25828.
|
|
Fixes assertion failure with fp-incomplete-tex (fdo 24298).
|
|
|
|
|
|
Rearrange things so that the writes to the dest registers happen
after we've fetched/used all src registers.
The problematic instruction was: XPD TEMP[2].xyz, TEMP[0], TEMP[2];
Note that the dst reg is also a src reg.
This fixes bad shading with progs/glsl/bump.c since Eric's changes to the
Mesa program optimizer in commit d6690ce15fb8c7c6abf1bc0d847c1d2da2c33904.
The optimizer rearranges some registers so we occasionally wind up with
something like the above.
|
|
Otherwise we risk overwriting them with temporary GPRs if
they're not used immediately after the CALL.
|
|
|
|
|