Am 15.02.2013 22:25, schrieb Vadim Girlin:
On 02/15/2013 03:22 PM, Christian König wrote:
Am 15.02.2013 12:00, schrieb Vadim Girlin:
[SNIP]
Heaven 3.0, all settings high/enabled, 1280x720, HD5750:
default backend : 20.0 fps
llvm backend: 18.8 fps
r600-sb : 38.0 fps
Quite
From the Ivy Bridge PRM, p268 (3DSTATE_SBE), in the description of
Point Sprite Texture Coordinate Enable:
This field must be programmed to 0 when non-point primitives are
rendered.
A similar admonishment exists in the Sandy Bridge PRM.
Although I'm not aware of any known bugs due to us
Pre-Gen6, the SF thread requires exact matching between VS output
slots (aka VUE slots) and FS input slots, even when the corresponding
VS output slot is unused due to being overwritten by point coordinate
replacement (glTexEnvi(GL_POINT_SPRITE, GL_COORD_REPLACE, GL_TRUE)).
As a result, we have a
On 15 February 2013 23:16, Eric Anholt e...@anholt.net wrote:
christopher.halse.rog...@canonical.com writes:
From: Christopher James Halse Rogers r...@ubuntu.com
_mesa_delete_renderbuffer does not call the driver-specific
renderbuffer delete function, so the blorp code was leaking the
https://bugs.freedesktop.org/show_bug.cgi?id=59777
--- Comment #1 from Brian Paul bri...@vmware.com ---
This test was failing way before commit
4a938ef7136a89c828ebb16effe1bc5bea08b7d7
I don't know if it ever passed.
--
You are receiving this mail because:
You are the assignee for the bug.
Am Dienstag, 5. Februar 2013, 17:29:20 schrieben Sie:
A single element in a GLX reply is contained in the header itself.
The number of elements is denoted in the n field of the reply, if
n is 1, the length of additional data is 0.
The XXX_data_length() function of xcb does not return the
On 02/16/2013 11:10 AM, Mathias � wrote:
Hi,
On Friday, February 15, 2013 15:00:24 Vadim Girlin wrote:
LLVM backend is the future is a pretty abstract argument. I prefer to
operate with real facts. After a year of LLVM backend development what
are the real benefits for the users? What are the
brw_vs_prog_data::userclip hasn't been used since commit f0cecd4
(i965: Move VUE map computation to once at VS compile time).
brw_gs_prog_key::userclip_active hasn't been used since commit 9f3d321
(i965: Make the userclip flag for the VUE map come from VS prog data).
---
This fixes a regression from ab74fee5e1a3fc3323b7238278637b232c2d0d95.
When we use the clip coordinate to compute the screen-space interpolation
factor, we need to first apply the divide-by-zero step to the clip
coordinate.
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=60938
Note: This is a
On 16 February 2013 10:58, Brian Paul bri...@vmware.com wrote:
This fixes a regression from ab74fee5e1a3fc3323b7238278637b232c2d0d95.
When we use the clip coordinate to compute the screen-space interpolation
factor, we need to first apply the divide-by-zero step to the clip
coordinate.
I
On Wed, Feb 13, 2013 at 1:43 PM, Tom Stellard t...@stellard.net wrote:
From: Tom Stellard thomas.stell...@amd.com
---
Candidate for the stable branch as well?
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On 02/16/2013 07:29 AM, Paul Berry wrote:
From the Ivy Bridge PRM, p268 (3DSTATE_SBE), in the description of
Point Sprite Texture Coordinate Enable:
This field must be programmed to 0 when non-point primitives are
rendered.
A similar admonishment exists in the Sandy Bridge PRM.
On 02/15/2013 10:26 PM, Eric Anholt wrote:
This should fix the register allocation explosion on the GLES 3.0
test on gen6.
Except that it doesn't. You can check by running it with
INTEL_DEVID_OVERRIDE=0x116.
A tiny change below makes it work though...
---
On 16 February 2013 13:52, Kenneth Graunke kenn...@whitecape.org wrote:
On 02/16/2013 07:29 AM, Paul Berry wrote:
From the Ivy Bridge PRM, p268 (3DSTATE_SBE), in the description of
Point Sprite Texture Coordinate Enable:
This field must be programmed to 0 when non-point primitives are
On Sat, Feb 16, 2013 at 12:17 PM, Paul Berry stereotype...@gmail.com wrote:
On 16 February 2013 10:58, Brian Paul bri...@vmware.com wrote:
This fixes a regression from ab74fee5e1a3fc3323b7238278637b232c2d0d95.
When we use the clip coordinate to compute the screen-space interpolation
factor,
On Sat, Feb 16, 2013 at 12:51:34PM -0800, Matt Turner wrote:
On Wed, Feb 13, 2013 at 1:43 PM, Tom Stellard t...@stellard.net wrote:
From: Tom Stellard thomas.stell...@amd.com
---
Candidate for the stable branch as well?
No, only LLVM 3.2 is supported in the stable branch.
-Tom
16 matches
Mail list logo
