Mesa now supports OpenGL 3.3 and GLSL 3.30, so bump the Mesa major
version from 10 to 11 to reflect this.
Also update the release notes, and add appropriate FAQ entries.
http://en.wikipedia.org/wiki/Up_to_eleven
Signed-off-by: Kenneth Graunke
Reviewed-by: Matt Turner
---
VERSION
Signed-off-by: Kenneth Graunke
Reviewed-by: Matt Turner
---
docs/relnotes/10.0.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/relnotes/10.0.html b/docs/relnotes/10.0.html
index 8f97921..0b25f49 100644
--- a/docs/relnotes/10.0.html
+++ b/docs/relnotes/10.0.htm
Everything necessary for these appears to be implemented. We'll want to
add more tests to guard against bugs, but it should be functionally
complete.
Signed-off-by: Kenneth Graunke
Reviewed-by: Matt Turner
---
src/mesa/drivers/dri/i965/intel_extensions.c | 2 +-
src/mesa/drivers/dri/i965/intel
All the necessary pieces are now in place.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/intel_extensions.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/intel_extensions.c
b/src/mesa/drivers/dri/i965/intel_extensions.c
index 334be05..c09ee39 1
Implementing the GetTransformFeedbackVertexCount() driver hook allows
the VBO module to call us with the right number of vertices.
The hardware doesn't directly count the number of vertices written by
SOL, so we instead use the SO_NUM_PRIMS_WRITTEN(n) counters and multiply
by the number of vertice
Renaming it makes it obvious that it isn't used, and the assertion
verifies that the VBO module never passes us such an object.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_draw.c | 4 +++-
src/mesa/drivers/dri/i965/brw_draw.h | 2 +-
2 files changed, 4 insertions(+), 2 delet
DrawTransformFeedback() needs to obtain the number of vertices written
to a particular stream during the last Begin/EndTransformFeedback block.
The new driver hook returns exactly that information.
Gallium drivers already implement this functionality by passing the
transform feedback object to the
This adds the basic driver hooks to allocate/free the brw variant.
It doesn't contain any additional information yet, but it will soon.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_context.c | 2 ++
src/mesa/drivers/dri/i965/brw_context.h | 9 +
src/mesa/drivers/dri
The ARB_transform_feedback2 extension introduces the ability to pause
and resume transform feedback sessions. Although only one can be active
at a time, it's possible to switch between multiple transform feedback
objects while paused.
In order to facilitate this, we need to save/restore the SO_WR
Here's my implementation of ARB_transform_feedback2. I believe it's
complete; it passes all of our Piglit tests and a lot of Intel's
oglconform tests.
This should work out of the box on Ivybridge and Baytrail. It won't
work on Haswell at the moment, due to restrictions on register writes
(to be
Since 062317d6671 (i965: Go back to using the kernel SOL reset feature.)
we've been flushing the batch on BeginTransformFeedback(). So it's not
necessary to do it on EndTransformFeedback(). A PIPE_CONTROL will work.
This makes gen7_end_transform_feedback() exactly the same as the gen6
variant.
The current callers just want to write a single register, so combining
the register read with a pipeline flush made sense. However, in the
future we'll want to do multiple register reads back to back, and we'll
only want to flush once.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i96
Writing a 64-bit register value to memory is sufficiently complicated
that it makes sense to reuse this function rather than duplicating it.
Exposing it outside of gen6_queryobj.c means it needs a more descriptive
function name. It could probably be moved to brw_util.c or somewhere
else, but this
On 10/17/2013 08:07 PM, Paul Berry wrote:
> Previously, Mesa followed the linkage rules outlined in the GLSL
> 1.20-1.40 specs, which (collectively) said that GLSL versions 1.10 and
> 1.20 could be linked together, but no other versions could be linked.
>
> In GLSL 4.30, the linkage rules were rel
Previously, Mesa followed the linkage rules outlined in the GLSL
1.20-1.40 specs, which (collectively) said that GLSL versions 1.10 and
1.20 could be linked together, but no other versions could be linked.
In GLSL 4.30, the linkage rules were relaxed so that any two desktop
GLSL versions can be li
>From 762d184225d5f4c6c46ff302725063483ebd8bf0 Mon Sep 17 00:00:00 2001
From: Daniel Czarnowski
Date: Thu, 17 Oct 2013 12:27:15 +0200
Subject: [PATCH] Enables the fbconfig_float extension in list of supported
extensions, and adds it to known extensions table.
---
glx/extension_string.c |5 +++
>From f93a54e7447a6f30c68d31ac82637e724c3953eb Mon Sep 17 00:00:00 2001
From: Daniel Czarnowski
Date: Wed, 16 Oct 2013 13:36:33 +0200
Subject: [PATCH] Support of GLX_RGBA*_FLOAT_BIT*, and correct setting of the
flags. Also commented each renderType use with information which (fbconfig
or contex
>From bf60ddd081bd66d1364bf7973e664af46335dfd6 Mon Sep 17 00:00:00 2001
From: Daniel Czarnowski
Date: Wed, 16 Oct 2013 13:35:20 +0200
Subject: [PATCH] Support of GLX_RGBA*_FLOAT_BIT*, and correct setting of the
flags. Also commented each renderType use with information
which (fbconfig or context)
Hello,
You can find attached a patch to apply on the include/GL/gl.h file.
This patch aims to fix a build issue with GCC when using the -DGL_GLEXT_LEGACY,
-Werror and -Wundef flags. I have remarked the problem with Qt 5.1.1 (which I
am packaging for NixOS) but it will occur on any build which c
Looks good. Thanks.
Reviewed-by: Jose Fonseca
Jose
- Original Message -
> MSVC doesn't have a strcasecmp() function; it uses _stricmp() instead.
> ---
> src/glsl/glsl_parser.yy | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/src/glsl/glsl_parser.yy b/sr
https://bugs.freedesktop.org/show_bug.cgi?id=70591
Priority: medium
Bug ID: 70591
Keywords: regression
CC: bri...@vmware.com
Assignee: mesa-dev@lists.freedesktop.org
Summary: glxext.h:275: error: redefinition of typedef
MSVC doesn't have a strcasecmp() function; it uses _stricmp() instead.
---
src/glsl/glsl_parser.yy | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/src/glsl/glsl_parser.yy b/src/glsl/glsl_parser.yy
index ba2dc63..00589e2 100644
--- a/src/glsl/glsl_parser.yy
+++ b/src/glsl
On 17 October 2013 12:35, Brian Paul wrote:
> Hi Paul,
>
> It looks like MSVC doesn't have the strcasecmp() function you recently
> employed in src/glsl/glsl_parser.yy.
>
> Looks like the work-around is _stricmp, per
> http://stackoverflow.com/**questions/3694723/error-c3861-**
> strcasecmp-ident
There is nothing in the OpenGL specification which prevents the user from
calling glGenQueries to generate a new query object while another object is
active. Neither is there anything in the Mesa implementation which prevents
this. So remove the INVALID_OPERATION errors in this case.
Similarly, it
On Wed, Oct 16, 2013 at 11:25 PM, Kenneth Graunke wrote:
> On 10/16/2013 03:49 PM, Ian Romanick wrote:
> [snip]
>> You are completely correct here. We should check what other vendors do.
>> I think 5 tests will tell us everything we need to know (then we'll
>> probably submit some spec bugs). I
Hi Paul,
It looks like MSVC doesn't have the strcasecmp() function you recently
employed in src/glsl/glsl_parser.yy.
Looks like the work-around is _stricmp, per
http://stackoverflow.com/questions/3694723/error-c3861-strcasecmp-identifier-not-found-in-visual-studio-2008/3694738#3694738
I'll lo
On 10/17/2013 12:14 PM, Carl Worth wrote:
There is nothing in the OpenGL specification which prevents the user from
calling glGenQueries to generate a new query object while another object is
active. Neither is there anything in the Mesa implementation which prevents
this. So remove the INVALID_O
https://bugs.freedesktop.org/show_bug.cgi?id=70581
Emil Velikov changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |emil.l.veli...@gmail.com
There is nothing in the OpenGL specification which prevents the user from
calling glGenQueries to generate a new query object while another object is
active. Neither is there anything in the Mesa implementation which prevents
this. So remove the INVALID_OPERATION errors in this case.
Similarly, it
https://bugs.freedesktop.org/show_bug.cgi?id=70546
Brian Paul changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=70581
Johannes Obermayr changed:
What|Removed |Added
CC||emil.l.veli...@gmail.com,
https://bugs.freedesktop.org/show_bug.cgi?id=70581
Priority: medium
Bug ID: 70581
Assignee: mesa-dev@lists.freedesktop.org
Summary: ./autogen.sh warnings in Mesa build system since
commit 4e9028b
Severity: normal
Classifi
Thanks.
Jose
- Original Message -
> * Based on ideas of Jose Fonseca
> * A rework of ce8eadb6e8
> ---
> scons/llvm.py | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/scons/llvm.py b/scons/llvm.py
> index c1c3736..8388d8e 100644
> --- a/scons/llvm.py
> +++ b/scons/llvm.py
>
On 16 October 2013 22:30, Kenneth Graunke wrote:
> On 10/16/2013 04:56 PM, Ian Romanick wrote:
> > On 10/16/2013 10:29 AM, Paul Berry wrote:
> >> ---
> >>
> >> I'm not 100% sure this is the right way to go, and here's why:
> >>
> >> Taken together, all the GLSL specs except GLSL 4.30 and GLSL 4.4
https://bugs.freedesktop.org/show_bug.cgi?id=70546
--- Comment #2 from Vinson Lee ---
(In reply to comment #1)
>
> If you remove lines 1739-1740 in gl.h does that fix this?
Yes, removing those two lines fixes the build.
diff --git a/include/GL/gl.h b/include/GL/gl.h
index 975cfe8..babb746 1006
On Thu, 2013-10-17 at 18:11 +0200, Johannes Obermayr wrote:
> Am Mittwoch, 16. Oktober 2013, 16:58:53 schrieb Alexander von Gluck:
> > On Wed, 2013-10-16 at 22:09 +0200, Johannes Obermayr wrote:
> > > Am Dienstag, 15. Oktober 2013, 17:22:54 schrieb Alexander von Gluck:
> > > > On Tue, 2013-10-15 at
On Thu, 17 Oct 2013 18:11:07 +0200
Johannes Obermayr wrote:
>
> Simply make llvm devs to push this fix to all branches (again my words: "Sth.
> like [...]):
Yeah, I can't make anyone do anything... you have to ask them nicely.
> diff --git a/tools/llvm-config/CMakeLists.txt
> b/tools/llvm-con
Am Mittwoch, 16. Oktober 2013, 16:58:53 schrieb Alexander von Gluck:
> On Wed, 2013-10-16 at 22:09 +0200, Johannes Obermayr wrote:
> > Am Dienstag, 15. Oktober 2013, 17:22:54 schrieb Alexander von Gluck:
> > > On Tue, 2013-10-15 at 15:05 -0700, Francisco Jerez wrote:
> > > > Johannes Obermayr writ
Although in principle there is no hardware limitation that prevents
gl_MaxGeometryInputComponents from being set to 128 on Gen7, we have
the following limitations in the vec4 compiler back end:
- Registers assigned to geometry shader inputs can't be spilled or
later re-used for any other purpose
Parallel change to "i965/gs: Fix up gl_PointSize input swizzling for
DUAL_INSTANCED gs.", except applied to the gl_PrimitiveID fixup
instead of the gl_PointSize fixup.
---
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 18 +-
src/mesa/drivers/dri/i965/brw_vec4_gs_visitor.cpp |
This is similar to what we do for 16-wide vs 8-wide fragment shaders.
First we try compiling the geometry shader in DUAL_OBJECT mode. If we
can't do that without spilling, we fall back on DUAL_INSTANCED mode,
which should require less spilling (since it uses an interleaved
layout of payload regist
Geometry shaders that run in "DUAL_INSTANCED" mode store their inputs
in vec4's. This means that when compiling gl_PointSize input
swizzling (a MOV instruction which uses a geometry shader input as
both source and destination), we need to do two things:
- Set force_writemask_all to ensure that th
Not yet enabled.
---
src/mesa/drivers/dri/i965/brw_context.h | 6 ++
src/mesa/drivers/dri/i965/brw_vec4_gs_visitor.cpp | 25 +--
src/mesa/drivers/dri/i965/brw_vec4_gs_visitor.h | 3 ++-
src/mesa/drivers/dri/i965/gen7_gs_state.c | 4 +++-
4 files chang
Otherwise the scheduler would be invoked with prog_data->total_grf ==
0, causing havoc.
In a future patch, this will allow us to try compiling a geometry
shader in DUAL_OBJECT mode with spilling disabled, and then fall back
to DUAL_INSTANCED mode if that failed.
---
src/mesa/drivers/dri/i965/brw_
In future patches, this will allow us to first try compiling a
geometry shader in DUAL_OBJECT mode (which is more efficient but uses
more registers) and then if spilling is required, fall back on
DUAL_INSTANCED mode.
---
src/mesa/drivers/dri/i965/brw_vec4.h | 9 -
src/
Previously, i965 geometry shaders always operated in DUAL_OBJECT mode,
which is similar to vertex shader operation in that two independent
sets of inputs get dispatched to a single SIMD4x2 geometry shader
thread, which executes them both in parallel.
When register usage is tight, we need to switch
When geometry shaders are operated in "single" or "dual instanced"
mode, a single set of geometry shader inputs is interleaved into the
thread payload (with each payload register containing a pair of
inputs) in order to save register space.
This patch modifies vec4_visitor::lower_attributes_to_hw_
---
src/glsl/ast_to_hir.cpp | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/src/glsl/ast_to_hir.cpp b/src/glsl/ast_to_hir.cpp
index dfa32d9..f96ed53 100644
--- a/src/glsl/ast_to_hir.cpp
+++ b/src/glsl/ast_to_hir.cpp
@@ -637,8 +637,8 @@ shift_result
> > To my knowledge, there exists only two implementations.
> >
> > ARM ships an implementation for Android on Mali. I don't see such
> > a spec update hurting ARM, because Android devices
> > are fairly locked down systems with a monolithic source tree for each
> > device.
>
> As far as I know, t
On Thu, Oct 17, 2013 at 3:29 PM, Chia-I Wu wrote:
> On Thu, Oct 17, 2013 at 1:53 PM, Chia-I Wu wrote:
>> Hi Eric,
>>
>> On Sat, Oct 12, 2013 at 3:18 AM, Eric Anholt wrote:
>>> Chia-I Wu writes:
>>>
Hi Eric,
The frame rate of Unigine Tropics (with low shader quality) dropped
from
On Thu, Oct 17, 2013 at 1:53 PM, Chia-I Wu wrote:
> Hi Eric,
>
> On Sat, Oct 12, 2013 at 3:18 AM, Eric Anholt wrote:
>> Chia-I Wu writes:
>>
>>> Hi Eric,
>>> The frame rate of Unigine Tropics (with low shader quality) dropped
>>> from 40.8 to 23.5 after this change.
>>
>> Thanks for the note. I
On Wed, Oct 16, 2013 at 11:57:16PM -0700, Paul Berry wrote:
>On 16 October 2013 23:29, Pohjolainen, Topi
>wrote:
>
> On Wed, Oct 16, 2013 at 11:13:33AM -0700, Paul Berry wrote:
> > The queries GEOMETRY_VERTICES_OUT, GEOMETRY_INPUT_TYPE, and
> > GEOMETRY_OUTPUT_TYPE (defined
On 16 October 2013 23:29, Pohjolainen, Topi wrote:
> On Wed, Oct 16, 2013 at 11:13:33AM -0700, Paul Berry wrote:
> > The queries GEOMETRY_VERTICES_OUT, GEOMETRY_INPUT_TYPE, and
> > GEOMETRY_OUTPUT_TYPE (defined by GL 3.2) differ from the corresponding
> > queries in ARB_geometry_shader4 in the fol
53 matches
Mail list logo
