| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
Check for these and route them to a dedicated handler with one fewer
levels of recursive rasterization.
|
| |
|
|
|
|
|
| |
No need to calculate these values any longer, nor to store them in the
bin data. Improves isosurf a bit more, 115->123 fps.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For 16 and 64 pixel levels, calculate a mask which is linear in x and
y (ie not in the swizzle layout).
When iterating over full and partial masks, figure out position by
manipulating the bit number set in the mask, rather than relying on
postion arrays.
Similarly, calculate the lower-level c values from dcdx, dcdy and the
position rather than relying on the step array.
|
| |
|
| |
|
|
|
|
| |
No noticable slowdown with isosurf.
|
|
|
|
|
| |
isosurf 95->115 fps just by exchanging the two inner loops in this
function...
|
| |
|
|
|
|
|
| |
Per Jakob's request. Not super-pretty, but it's a good point for modding
later.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This skips the blitter clear path entirely if the color is not cleared and
the depth+stencil is cleared with the ZMask.
|
|
|
|
| |
z_fastfill -> dirty_zmask[level].
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This commit silences the printing off most of the debug information
when running debug builds. The big culprits are: the tgsi sanity checker
that gets run on all shaders on debug; all the options; and
finaly the cpu caps printer.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This logic duplicates the one in p_config.h, so remove it and adjust
the only two places that were using it.
|
|
|
|
| |
It causes a very ugly corruption on the Earth's halo on Google Earth.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is based on a patch by nobled <[email protected]> and allows the TFP
extension to be enabled for DRISW also. This patch does not enable TFP for DRISW
though, because testing on xephyr segfaults here (for both classic and gallium):
Program received signal SIGSEGV, Segmentation fault.
0x00786a4a in _mesa_GenTextures (n=1, textures=0xbfffee4c) at main/texobj.c:788
788 ASSERT_OUTSIDE_BEGIN_END(ctx);
(gdb)
(gdb) where
\#0 0x00786a4a in _mesa_GenTextures (n=1, textures=0xbfffee4c) at main/texobj.c:788
\#1 0x0817a004 in __glXDisp_GenTextures ()
\#2 0x08168498 in __glXDispatch ()
\#3 0x0808b6ce in Dispatch ()
\#4 0x08084435 in main ()
The TFP code is generic except for the teximage call. We need to verify that
DRISW correclty implements whatever hook teximage finally calls.
|
| |
|
| |
|
|
|
|
| |
It doesn't work well with Hyper-Z, so put the burden on the state tracker.
|
|
|
|
| |
This always restores the previous depth clear value after CBZB clear.
|
|
|
|
|
|
| |
Sent on ML by Владимир.
These values are what fglrx returns.
|
|
|
|
|
|
|
| |
It breaks Regnum Online in that it renders random triangles
all over the screen.
https://bugs.freedesktop.org/show_bug.cgi?id=29518
|
| |
|
|
|
|
|
| |
I noticed gears memory usage was heading skywards, some r600 "states"
aren't properly refcounted, and the ctx->state is never freed.
|
| |
|
|
|
|
| |
Use a kludgy function based on rand() instead of drand48()
|
|
|
|
|
|
|
| |
1. Generate random data specifically for float and doubles, so that
they end up in [0, 1] range
2. Don't test useless conversions like SCALED <-> NORM
3. Poison the buffers before testing
|
|
|
|
| |
This reverts commit de4784e36505316c2a5ab34cc5b371d17f38d3c5.
|
|
|
|
| |
fixes piglit stencil-twoside and stencil-wrap
|
| |
|
|
|
|
|
|
|
|
|
| |
This takes the r300g texture format checker and fixes it up for r600g,
it passes glean texSwizzle, pixelformats, and texture_srgb tests,
however I think it L8S8_SRGB is broken as is L8_SRGB, need to investigate.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
| |
No need to enable depth test for clear.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
1. Fix the segfault due to the reverted commit using the new interface
2. Reindent to Mesa 3 spaces style
3. Improve output and return success/failure with error code
4. Add much better support for testing translate_sse
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently translate asserts on unsupported output formats, making
it impossible to use for some purposes, such as testing whether it
actually works on all formats it supports.
Removing the assert was met with opposition, so this change allows
clients to ask whether an output format is supported, and they are thus
able to avoid attempting to use it.
Since this is just an addition to the API, no adverse effect is
possible, and it makes the testsuite work again.
|