On 12-01-18 01:11 PM, Eric Anholt wrote:
> On Tue, 17 Jan 2012 15:58:11 -0500, Matt Turner wrote:
>
> As far as I can tell, the point of AM_CPPFLAGS existing is if you want
> to make a target that separately calls the preprocessor, so you a list
> of includes and a list of non-preprocessor compile
On 12-01-17 08:30 PM, Matt Turner wrote:
> On Tue, Jan 17, 2012 at 7:32 PM, Gaetan Nadon wrote:
>> On 12-01-17 03:58 PM, Matt Turner wrote:
>>
>> +AM_CPPFLAGS = \
>> +-I$(top_srcdir)/include \
>> +-I$(top_srcdir)/src/ \
>> +-I$(top_srcdir)/src/mapi \
>> +-I$(top_srcdir)/src/mesa/ \
On 12-01-17 08:28 PM, Matt Turner wrote:
> On Tue, Jan 17, 2012 at 7:21 PM, Gaetan Nadon wrote:
>> On 12-01-17 03:58 PM, Matt Turner wrote:
>>> ---
>>> src/mesa/drivers/dri/i965/Makefile.am |4 +---
>>> 1 files changed, 1 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/src/mesa/drivers/dri
When rendering to FBO, rendering is inverted. At the same time, we would
also make sure the point sprite origin is inverted. Or, we will get an
inverted result correspoinding to rendering to the default winsys FBO.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44613
NOTE: This is a candi
On Wed, Jan 18, 2012 at 11:53:20AM -0800, Ian Romanick wrote:
> On 01/18/2012 02:23 AM, Yuanhan Liu wrote:
> >When rendering to FBO, rendering is inverted. At the same time, we would
> >also make sure the point sprite origin is inverted. Or, we will get an
> >inverted result correspoinding to rende
On Wed, Jan 18, 2012 at 12:13:28PM -0800, Ian Romanick wrote:
> On 01/18/2012 02:21 AM, Yuanhan Liu wrote:
> >On Wed, Jan 18, 2012 at 06:23:52PM +0800, Yuanhan Liu wrote:
> >>When rendering to FBO, rendering is inverted. At the same time, we would
> >>also make sure the point sprite origin is inver
AC_CHECK_LIB has this nasty behavior, like the cflags tests, of
automatically putting the tested value into the global LIBS on
success. This caused -lexpat to end up in LIBS, but without the
--with-expat dir, so my 32-bit build on a 64 system using expat from a
custom prefix could only find the sy
Am Mittwoch, den 18.01.2012, 21:54 +0100 schrieb Patrice Mandin:
> Le Tue, 17 Jan 2012 18:22:59 +0100
> Patrice Mandin a écrit:
>
> > Le Tue, 10 Jan 2012 12:41:04 +0100
> > Lucas Stach a écrit:
> >
> > > Signed-off-by: Lucas Stach
> > > ---
> > > src/gallium/drivers/nvfx/nvfx_state_emit.c |
On Wed, 2012-01-18 at 21:49 +, Dave Airlie wrote:
> From: Dave Airlie
>
> So it appears R600s (except rv670) do AR handling different using a different
> opcode. This patch fixes up r600g to work properly on r600.
>
> This fixes ~100 piglit tests here (in GLSL1.30 mode) on rv610.
>
> v3: ad
On 01/18/2012 12:32 PM, Paul Berry wrote:
Commit ede60bc4670a8d9c14921c77abee1ac57fc0e6bf (glsl: Add isinf() and
isnan() builtins) uses "+INF" in the .ir file to represent infinity.
This worked on C99-compliant compilers, since the s-expression reader
uses strtod() to read numbers, and C99 requir
Shaves a few instructions off of the VS in Lightsmark, but no
statistically significant performance difference on gen7 (n=5).
---
src/mesa/drivers/dri/i965/brw_vec4_visitor.cpp | 22 --
1 files changed, 16 insertions(+), 6 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/
This is similar to a commit that did the same for the FS.
Shaves several more instructions off of the VS in Lightsmark, but no
statistically significant performance difference (n=5).
---
src/mesa/drivers/dri/i965/brw_vec4_visitor.cpp |8 ++--
1 files changed, 6 insertions(+), 2 deletions(
Well spotted, thanks!
Reviewed-by: Marek Olšák
Marek
On Wed, Jan 18, 2012 at 10:46 AM, Vadim Girlin wrote:
> Enable it in the evergreen_context_draw if needed.
> Same as already done in the r600_context_draw for r6xx/r7xx.
>
> Signed-off-by: Vadim Girlin
> ---
> src/gallium/drivers/r600/ever
From: Dave Airlie
So it appears R600s (except rv670) do AR handling different using a different
opcode. This patch fixes up r600g to work properly on r600.
This fixes ~100 piglit tests here (in GLSL1.30 mode) on rv610.
v3: add index_mode as per the docs.
This still fails any dst relative tests
On 18 January 2012 12:43, Jose Fonseca wrote:
> Looks good to me. Thanks
>
> Should there be a case for -INF while we are at it?
>
I think you can make arguments both for and against. On the one hand, C99
requires strtod to recognize "INF", "+INF", "-INF", "INFINITY",
"+INFINITY", "-INFINITY",
Le Tue, 17 Jan 2012 18:22:59 +0100
Patrice Mandin a écrit:
> Le Tue, 10 Jan 2012 12:41:04 +0100
> Lucas Stach a écrit:
>
> > Signed-off-by: Lucas Stach
> > ---
> > src/gallium/drivers/nvfx/nvfx_state_emit.c | 49
> > ---
> > 1 files changed, 22 insertions(+), 27 del
Looks good to me. Thanks
Should there be a case for -INF while we are at it?
Jose
- Original Message -
> Commit ede60bc4670a8d9c14921c77abee1ac57fc0e6bf (glsl: Add isinf()
> and
> isnan() builtins) uses "+INF" in the .ir file to represent infinity.
> This worked on C99-compliant compiler
https://bugs.freedesktop.org/show_bug.cgi?id=44912
Bug #: 44912
Summary: [bisected] WebGL conformance/textures/texture-mips
tests fails
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
Commit ede60bc4670a8d9c14921c77abee1ac57fc0e6bf (glsl: Add isinf() and
isnan() builtins) uses "+INF" in the .ir file to represent infinity.
This worked on C99-compliant compilers, since the s-expression reader
uses strtod() to read numbers, and C99 requires strtod() to understand
"+INF". However,
--- snip
Supporting Z32 -> Z32_FLOAT is a bad idea. So I've amended the patch
to avoid that.
--- end snip
This loosens the format validation in glBlitFramebuffer. When blitting
depth bits, don't require an exact match between the depth formats; only
require that the two formats have the same nu
On 01/18/2012 12:41 PM, Ian Romanick wrote:
From: Ian Romanick
The default access flags for OpenGL ES (via GL_OES_map_buffer) and
desktop OpenGL are different. The code previously tried to handle
this, but the decision was made at compile time. Since the same
driver binary can be used for both
On 01/18/2012 02:21 AM, Yuanhan Liu wrote:
On Wed, Jan 18, 2012 at 06:23:52PM +0800, Yuanhan Liu wrote:
When rendering to FBO, rendering is inverted. At the same time, we would
also make sure the point sprite origin is inverted. Or, we will get an
inverted result correspoinding to rendering to t
On 01/17/2012 02:58 PM, Brian Paul wrote:
On 01/16/2012 08:30 PM, Brian Paul wrote:
On Mon, Jan 16, 2012 at 4:31 PM, Ian Romanick wrote:
On 01/16/2012 01:30 PM, Brian Paul wrote:
The renderbuffer-cleanups-v2 branch removes all the old swrast
GetRow/PutRow stuff. All swrast rendering is now d
On 01/18/2012 02:23 AM, Yuanhan Liu wrote:
When rendering to FBO, rendering is inverted. At the same time, we would
also make sure the point sprite origin is inverted. Or, we will get an
inverted result correspoinding to rendering to the default winsys FBO.
Bugzilla: https://bugs.freedesktop.org
From: Ian Romanick
The default access flags for OpenGL ES (via GL_OES_map_buffer) and
desktop OpenGL are different. The code previously tried to handle
this, but the decision was made at compile time. Since the same
driver binary can be used for both OpenGL ES and desktop OpenGL, the
decision m
BURST_COUNT is clipped with ARRAY_SIZE, so set it to the max value
to avoid clipping.
Signed-off-by: Vadim Girlin
---
src/gallium/drivers/r600/r600_shader.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_shader.c
b/src/gallium/drivers/r
From: Dave Airlie
So it appears R600s (except rv670) do AR handling different using a different
opcode. This patch fixes up r600g to work properly on r600.
This fixes ~100 piglit tests here (in GLSL1.30 mode) on rv610.
Signed-off-by: Dave Airlie
---
src/gallium/drivers/r600/r600_asm.c|
On Tue, 17 Jan 2012 15:58:11 -0500, Matt Turner wrote:
As far as I can tell, the point of AM_CPPFLAGS existing is if you want
to make a target that separately calls the preprocessor, so you a list
of includes and a list of non-preprocessor compiler flags. Given that
we don't have any preprocesso
On Tue, 17 Jan 2012 08:19:44 -0700, Brian Paul wrote:
> Update the dd.h docs to indicate that GL_MAP_INVALIDATE_RANGE_BIT
> can be used with GL_MAP_WRITE_BIT when mapping renderbuffers and
> texture images.
>
> Pass the flag when mapping texture images for glTexImage, glTexSubImage,
> etc. It's
On Tue, Jan 17, 2012 at 6:10 PM, Brian Paul wrote:
> On 01/16/2012 04:45 PM, nobled wrote:
>>
>> glGetTexImage, for example, has no width/height/depth parameters.
>>
>> Also, copy some missing parameter info from the original versions
>> of certain functions over to their ARB_robustness counterpar
https://bugs.freedesktop.org/show_bug.cgi?id=44039
--- Comment #7 from Brian Paul 2012-01-18 09:47:45 PST ---
I've pushed the 16-bit float fallback work-around. Commit
7628696004515074594d4fdac4e422c81c86b32c
Nikita, Mathieu: can you re-test with Mesa/master?
--
Configure bugmail: https://bug
On Tue, 17 Jan 2012 22:10:07 -0800, Kenneth Graunke
wrote:
> Both the VF and VS share space in the URB. First, the VF stores
> attributes (shader inputs) there. The VS then reads the attributes,
> executes, and reuses the space to store varyings (shader outputs).
>
> Thus, we need to calculate
On 01/18/2012 09:01 AM, Dee Sharpe wrote:
While implementing Clear() for a platform, which buffers in GLContext need to
be cleared out of the list of:
DrawBuffer
ReadBuffer
WinSysDrawBuffer
WinSysReadBuffer
Or do they all need to be cleared?
Clearing effects "draw" buffers, not "read" buffer
While implementing Clear() for a platform, which buffers in GLContext need to
be cleared out of the list of:
DrawBuffer
ReadBuffer
WinSysDrawBuffer
WinSysReadBuffer
Or do they all need to be cleared?
A. Demetrious Sharpe
___
mesa-dev mailing list
mesa
On 01/17/2012 11:00 PM, Kenneth Graunke wrote:
On 01/17/2012 05:27 PM, Ian Romanick wrote:
On 01/17/2012 05:12 PM, Chad Versace wrote:
This reverts commit 3f1fab06844f696de44d9a56e83ff62e8ea576bd.
This loosens the format validation in glBlitFramebuffer. When blitting
depth bits, don't require
https://bugs.freedesktop.org/show_bug.cgi?id=24572
Michel Dänzer changed:
What|Removed |Added
AssignedTo|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
On Wed, Jan 18, 2012 at 06:23:52PM +0800, Yuanhan Liu wrote:
> When rendering to FBO, rendering is inverted. At the same time, we would
> also make sure the point sprite origin is inverted. Or, we will get an
> inverted result correspoinding to rendering to the default winsys FBO.
>
> Bugzilla: ht
When rendering to FBO, rendering is inverted. At the same time, we would
also make sure the point sprite origin is inverted. Or, we will get an
inverted result correspoinding to rendering to the default winsys FBO.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44613
Signed-off-by: Yuanha
Enable it in the evergreen_context_draw if needed.
Same as already done in the r600_context_draw for r6xx/r7xx.
Signed-off-by: Vadim Girlin
---
src/gallium/drivers/r600/evergreen_hw_context.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/src/gallium/drivers/r600/e
- Original Message -
> On Tue, Jan 17, 2012 at 15:47, Stéphane Marchesin
> wrote:
> > On Wed, Jan 11, 2012 at 10:13, Jose Fonseca
> > wrote:
> >> - Original Message -
> >>> Where else would the flush go?
> >>
> >> Maybe one of the callers already invoked glFlush, or something
>
40 matches
Mail list logo
