Marek, do you have an idea on where the currency bottleneck is?
I just did a profiling with sysprof, zooming in on the desktop in Weston
and moving the mouse wildly around, so that the buffer is completely
changed for every frame. I got around 5 fps, which isn't *that* much, but
still an order of
Pushed, except for creating a page in mesa/docs. I'll do that some time later.
Marek
On Mon, Mar 25, 2013 at 3:45 PM, Brian Paul wrote:
> On 03/22/2013 05:50 PM, Marek Olšák wrote:
>>
>> Hi everyone, one image is better than a thousand words:
>>
>> http://people.freedesktop.org/~mareko/gallium-h
Verify that interface blocks match when linking separate shader
stages into a program.
Fixes piglit glsl-1.50 tests:
* linker/interface-blocks-vs-fs-member-count-mismatch.shader_test
* linker/interface-blocks-vs-fs-member-order-mismatch.shader_test
Signed-off-by: Jordan Justen
---
src/glsl/inte
With this change we now support interface block arrays.
For example, cases like this:
out block_name {
float f;
} block_instance[2];
This allows Mesa to pass the piglit glsl-1.50 test:
* execution/interface-blocks-complex-vs-fs.shader_test
Signed-off-by: Jordan Justen
---
src/glsl/lower_na
Signed-off-by: Jordan Justen
---
src/glsl/link_varyings.cpp | 33 +
1 file changed, 29 insertions(+), 4 deletions(-)
diff --git a/src/glsl/link_varyings.cpp b/src/glsl/link_varyings.cpp
index 04c9fdd..b374049 100644
--- a/src/glsl/link_varyings.cpp
+++ b/src/gls
Convert interface blocks with instance names into flat
interface blocks without an instance name.
Signed-off-by: Jordan Justen
---
src/glsl/Makefile.sources |1 +
src/glsl/ir_optimization.h|1 +
src/glsl/linker.cpp |6 +
src/glsl/
Verify that interface blocks match when combining compilation
units at the same stage. (For example, when merging all vertex
shaders.)
Fixes piglit glsl-1.50 test:
* linker/interface-blocks-multiple-vs-member-count-mismatch.shader_test
Signed-off-by: Jordan Justen
---
src/glsl/Makefile.sources
Signed-off-by: Jordan Justen
Reviewed-by: Kenneth Graunke
---
src/glsl/ast_to_hir.cpp | 28 ++--
1 file changed, 22 insertions(+), 6 deletions(-)
diff --git a/src/glsl/ast_to_hir.cpp b/src/glsl/ast_to_hir.cpp
index 25fcee4..8005fbd 100644
--- a/src/glsl/ast_to_hir.cpp
For interface blocks, there are three separate namespaces for
uniform, input and output blocks.
Signed-off-by: Jordan Justen
---
src/glsl/glsl_symbol_table.cpp | 84 ++--
src/glsl/glsl_symbol_table.h |4 ++
2 files changed, 85 insertions(+), 3 deletion
Signed-off-by: Jordan Justen
---
src/glsl/ast_to_hir.cpp |6 ++
1 file changed, 6 insertions(+)
diff --git a/src/glsl/ast_to_hir.cpp b/src/glsl/ast_to_hir.cpp
index 40f3188..612b3e4 100644
--- a/src/glsl/ast_to_hir.cpp
+++ b/src/glsl/ast_to_hir.cpp
@@ -4187,6 +4187,12 @@ ast_process_stru
Interface blocks in GLSL 150 allow an instance name to be used.
v2:
* use state->check_version
Signed-off-by: Jordan Justen
Reviewed-by: Eric Anholt
Reviewed-by: Kenneth Graunke
---
src/glsl/glsl_parser.yy |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/src/gls
git://people.freedesktop.org/~jljusten/mesa interface-blocks-v3
v3:
* Several clean-ups based on v2 code review
* Fix (proposed) piglit test:
execution/interface-blocks-same-uniform-varying-name.shader_test
(varying interface block having the same name as a uniform
interface block.)
*
Signed-off-by: Jordan Justen
---
src/glsl/ast_to_hir.cpp |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/glsl/ast_to_hir.cpp b/src/glsl/ast_to_hir.cpp
index 9913309..25fcee4 100644
--- a/src/glsl/ast_to_hir.cpp
+++ b/src/glsl/ast_to_hir.cpp
@@ -4178,7 +4178,11 @@ a
Signed-off-by: Jordan Justen
Reviewed-by: Eric Anholt
Reviewed-by: Kenneth Graunke
---
src/glsl/ast.h |4 ++--
src/glsl/ast_to_hir.cpp |6 +++---
src/glsl/glsl_parser.yy | 14 +++---
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/glsl/ast.h b/src
Previously uniform blocks allowed for the 'uniform' keyword
to be used with members of a uniform blocks. With interface
blocks 'in' can be used on 'in' interface block members and
'out' can be used on 'out' interface block members.
The basic_interface_block rule will verify that the same
qualifier
Uniform/interface blocks are a separate namespace from types.
Signed-off-by: Jordan Justen
---
src/glsl/ast_to_hir.cpp |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/glsl/ast_to_hir.cpp b/src/glsl/ast_to_hir.cpp
index 612b3e4..9913309 100644
--- a/src/glsl/ast_to_hir.
Signed-off-by: Jordan Justen
Reviewed-by: Eric Anholt
Reviewed-by: Kenneth Graunke
---
src/glsl/glsl_parser.yy | 14 ++
1 file changed, 14 insertions(+)
diff --git a/src/glsl/glsl_parser.yy b/src/glsl/glsl_parser.yy
index 0a2a77b..dbc25a4 100644
--- a/src/glsl/glsl_parser.yy
+++
An interface block member may specify the type:
in {
in vec4 in_var_with_qualifier;
};
When specified with the member, it must match the same
type as interface block type.
It can also omit the qualifier:
uniform {
vec4 uniform_var_without_qualifier;
};
When the type is not specified with
Previously only 'uniform' was allowed for uniform blocks.
Now, in/out can be parsed, but it will only be allowed for
GLSL >= 150.
Signed-off-by: Jordan Justen
Reviewed-by: Eric Anholt
---
src/glsl/glsl_parser.yy | 51 +--
1 file changed, 40 inserti
Signed-off-by: Jordan Justen
Reviewed-by: Eric Anholt
Reviewed-by: Kenneth Graunke
---
src/glsl/glsl_parser.yy | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/glsl/glsl_parser.yy b/src/glsl/glsl_parser.yy
index cd33078..33b74ea 100644
--- a/s
>> + char *name = gr->name;
>> +
>> + /* replace '-' with a space */
>
>
> why?
For convenience. I wouldn't like to have space characters in the query
names in the environment variable, but I'd like to have spaces when
it's printed on the screen. For example, GALLIUM_HUD=pixels-rendered
and "p
Go ahead and push yours.
Reviewed-by: Brian Paul
On 03/25/2013 04:03 PM, Marek Olšák wrote:
I sent almost the same patch 3 days ago. I should have given it a
better commit message:
http://www.mail-archive.com/mesa-dev@lists.freedesktop.org/msg36038.html
Marek
On Mon, Mar 25, 2013 at 10:54 P
On Mon, Mar 25, 2013 at 6:11 PM, Martin Andersson wrote:
> Virtual address is used for PIPE_QUERY_SO* queries in
> r600_emit_query_begin, but not in r600_emit_query_end.
>
> This will trigger a GPU fault when one of those queries is
> made and virtual address is enabled.
Should also go to the 9.1
Virtual address is used for PIPE_QUERY_SO* queries in
r600_emit_query_begin, but not in r600_emit_query_end.
This will trigger a GPU fault when one of those queries is
made and virtual address is enabled.
---
src/gallium/drivers/r600/r600_query.c | 5 +++--
1 file changed, 3 insertions(+), 2 dele
I sent almost the same patch 3 days ago. I should have given it a
better commit message:
http://www.mail-archive.com/mesa-dev@lists.freedesktop.org/msg36038.html
Marek
On Mon, Mar 25, 2013 at 10:54 PM, Brian Paul wrote:
> Fixes uninitialized member bug spotted by Ondrej Holecek.
>
> Note: This
On Mon, Mar 25, 2013 at 10:38 PM, Ondrej Holecek wrote:
> On Saturday 23 of March 2013 00:50:59 Marek Olšák wrote:
>> Hi everyone, one image is better than a thousand words:
>> ...
>
> Hi,
>
> I tried your patches and hit a few problems. As first, they do not apply
> cleanly on master as they are
Fixes uninitialized member bug spotted by Ondrej Holecek.
Note: This is a candidate for the stable branches.
---
src/gallium/auxiliary/tgsi/tgsi_text.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/gallium/auxiliary/tgsi/tgsi_text.c
b/src/gallium/auxiliary/tgsi/tg
On 03/25/2013 03:38 PM, Ondrej Holecek wrote:
On Saturday 23 of March 2013 00:50:59 Marek Olšák wrote:
Hi everyone, one image is better than a thousand words:
...
Hi,
I tried your patches and hit a few problems. As first, they do not apply
cleanly on master as they are expecting another your
On Saturday 23 of March 2013 00:50:59 Marek Olšák wrote:
> Hi everyone, one image is better than a thousand words:
> ...
Hi,
I tried your patches and hit a few problems. As first, they do not apply
cleanly on master as they are expecting another your patch "cso: add constant
buffer save/restore
On Mon, Mar 25, 2013 at 9:28 PM, Rob Clark wrote:
> On Mon, Mar 25, 2013 at 3:27 PM, Erik Faye-Lund wrote:
>> On Mon, Mar 25, 2013 at 6:36 PM, Erik Faye-Lund wrote:
>>> On Mon, Mar 25, 2013 at 6:25 PM, Erik Faye-Lund wrote:
Signed-off-by: Erik Faye-Lund
---
I just peeked in
On Mon, Mar 25, 2013 at 6:14 PM, Jose Fonseca wrote:
>
>
> - Original Message -
>> Hi everyone, one image is better than a thousand words:
>>
>> http://people.freedesktop.org/~mareko/gallium-hud.png
>>
>> So there you have it. This gallium module can draw transparent graphs and
>> text on
That's a very good question. There are a couple of reasons for this.
1) Writing any kind of meta operation and custom rendering code on top
of GL is a horrible idea and very prone to errors. If you don't
restore all states after you're done, you may break the application.
If the application sets a
On Mon, Mar 25, 2013 at 3:27 PM, Erik Faye-Lund wrote:
> On Mon, Mar 25, 2013 at 6:36 PM, Erik Faye-Lund wrote:
>> On Mon, Mar 25, 2013 at 6:25 PM, Erik Faye-Lund wrote:
>>> Signed-off-by: Erik Faye-Lund
>>> ---
>>>
>>> I just peeked into the freedreno code, and noticed that it had some
>>> und
On Mon, Mar 25, 2013 at 6:36 PM, Erik Faye-Lund wrote:
> On Mon, Mar 25, 2013 at 6:25 PM, Erik Faye-Lund wrote:
>> Signed-off-by: Erik Faye-Lund
>> ---
>>
>> I just peeked into the freedreno code, and noticed that it had some
>> undocumented debug-code. Perhaps it could make sense to document it
On 03/23/2013 02:05 PM, gregory hainaut wrote:
On Fri, 22 Mar 2013 15:44:07 -0700
Matt Turner wrote:
On Fri, Mar 22, 2013 at 1:00 PM, gregory hainaut
wrote:
* GenProgramPipelines doesn't create object!
... Spec extract:
These names are marked as used, for the purposes of GenBuffers only,
- Original Message -
> ---
> src/gallium/auxiliary/gallivm/lp_bld_misc.cpp |8
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
> b/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
> index 6a560df..46cdbad 100644
>
On Mon, Mar 25, 2013 at 6:25 PM, Erik Faye-Lund wrote:
> Signed-off-by: Erik Faye-Lund
> ---
>
> I just peeked into the freedreno code, and noticed that it had some
> undocumented debug-code. Perhaps it could make sense to document it,
> like this?
>
> src/gallium/docs/source/debugging.rst | 4 +
Signed-off-by: Erik Faye-Lund
---
I just peeked into the freedreno code, and noticed that it had some
undocumented debug-code. Perhaps it could make sense to document it,
like this?
src/gallium/docs/source/debugging.rst | 4
1 file changed, 4 insertions(+)
diff --git a/src/gallium/docs/so
On Mon, Mar 25, 2013 at 1:12 PM, Christian König
wrote:
> Am 25.03.2013 17:50, schrieb Jerome Glisse:
>
>> On Mon, Mar 25, 2013 at 12:38 PM, Christian König
>> wrote:
>>>
>>> Am 25.03.2013 17:01, schrieb j.gli...@gmail.com:
>>>
From: Jerome Glisse
Same as on r600, trace cs executi
- Original Message -
> Hi everyone, one image is better than a thousand words:
>
> http://people.freedesktop.org/~mareko/gallium-hud.png
>
> So there you have it. This gallium module can draw transparent graphs and
> text on top of what apps are rendering. By default, it can show framer
From: Jerome Glisse
Same as on r600, trace cs execution by writting cs offset after each
states, this allow to pin point lockup inside command stream and
narrow down the scope of lockup investigation.
v2: Use WRITE_DATA packet instead of WRITE_MEM
Signed-off-by: Jerome Glisse
---
src/gallium/
Am 25.03.2013 17:50, schrieb Jerome Glisse:
On Mon, Mar 25, 2013 at 12:38 PM, Christian König
wrote:
Am 25.03.2013 17:01, schrieb j.gli...@gmail.com:
From: Jerome Glisse
Same as on r600, trace cs execution by writting cs offset after each
states, this allow to pin point lockup inside comman
On Mon, Mar 25, 2013 at 9:41 AM, violin yanev wrote:
> Hello,
>
> I was eager to try the OpenGL ES 3.0 support on the newest Mesa 9.1.
>
> I installed the latest Fedora Rawhide on my Sandy Bridge.
I believe this Fedora commit which disabled GL3 for Intel graphics
will also disable GLES3 for Intel
On Mon, Mar 25, 2013 at 9:41 AM, violin yanev wrote:
> Hello,
>
> I was eager to try the OpenGL ES 3.0 support on the newest Mesa 9.1.
>
> I installed the latest Fedora Rawhide on my Sandy Bridge. I think the
> graphics chip is HD 2000, lspci says I have a Xeon E3-1200 V2/3rd gen
> processor. glxi
On Mon, Mar 25, 2013 at 12:38 PM, Christian König
wrote:
> Am 25.03.2013 17:01, schrieb j.gli...@gmail.com:
>
>> From: Jerome Glisse
>>
>> Same as on r600, trace cs execution by writting cs offset after each
>> states, this allow to pin point lockup inside command stream and
>> narrow down the sc
I feel rather awkward asking, but: why implement this inside of
Gallium, instead of as a standalone {egl,glX}SwapBuffers interceptor
obtaining counter values via GL extensions, such as
ARB_occlusion_query or AMD_performance_monitor? That way Intel (and
Nouveau?) people could also benefit from it.
Hello,
I was eager to try the OpenGL ES 3.0 support on the newest Mesa 9.1.
I installed the latest Fedora Rawhide on my Sandy Bridge. I think the
graphics chip is HD 2000, lspci says I have a Xeon E3-1200 V2/3rd gen
processor. glxinfo states that I have Mesa 9.1, and lsmod lists i915 as my
VGA dr
Am 25.03.2013 17:01, schrieb j.gli...@gmail.com:
From: Jerome Glisse
Same as on r600, trace cs execution by writting cs offset after each
states, this allow to pin point lockup inside command stream and
narrow down the scope of lockup investigation.
Signed-off-by: Jerome Glisse
Could your r
On Mon, Mar 25, 2013 at 12:01 PM, wrote:
> From: Jerome Glisse
>
> Same as on r600, trace cs execution by writting cs offset after each
> states, this allow to pin point lockup inside command stream and
> narrow down the scope of lockup investigation.
>
> Signed-off-by: Jerome Glisse
> ---
> s
On Mon, Mar 25, 2013 at 12:17 PM, Michel Dänzer wrote:
> On Mon, 2013-03-25 at 12:01 -0400, j.gli...@gmail.com wrote:
>> From: Jerome Glisse
>>
>> Same as on r600, trace cs execution by writting cs offset after each
>> states, this allow to pin point lockup inside command stream and
>> narrow dow
---
src/gallium/auxiliary/gallivm/lp_bld_misc.cpp |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
b/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
index 6a560df..46cdbad 100644
--- a/src/gallium/auxiliary/gallivm/lp_bld_
---
src/gallium/drivers/llvmpipe/lp_state_fs.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/llvmpipe/lp_state_fs.c
b/src/gallium/drivers/llvmpipe/lp_state_fs.c
index b87e1a4..de51f39 100644
--- a/src/gallium/drivers/llvmpipe/lp_state_fs.c
+++ b/s
---
src/mesa/swrast/s_blit.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/mesa/swrast/s_blit.c b/src/mesa/swrast/s_blit.c
index 82fa43f..051354d 100644
--- a/src/mesa/swrast/s_blit.c
+++ b/src/mesa/swrast/s_blit.c
@@ -110,8 +110,8 @@ blit_nearest(struct gl_co
On Mon, 2013-03-25 at 12:01 -0400, j.gli...@gmail.com wrote:
> From: Jerome Glisse
>
> Same as on r600, trace cs execution by writting cs offset after each
> states, this allow to pin point lockup inside command stream and
> narrow down the scope of lockup investigation.
>
> Signed-off-by: Jero
From: Jerome Glisse
Same as on r600, trace cs execution by writting cs offset after each
states, this allow to pin point lockup inside command stream and
narrow down the scope of lockup investigation.
Signed-off-by: Jerome Glisse
---
src/gallium/drivers/radeonsi/r600_hw_context.c | 58
Paul Berry writes:
> Gen7 adds mask bits to the message header for a URB write which allow
> the write to apply only to certain channels. We don't use this
> functionality, so to ensure that the entire write always occurs, we
> emit an OR instruction to set the mask bits.
>
> With the advent of
On 03/25/2013 08:45 AM, Brian Paul wrote:
On 03/22/2013 05:50 PM, Marek Olšák wrote:
Hi everyone, one image is better than a thousand words:
http://people.freedesktop.org/~mareko/gallium-hud.png
So there you have it. This gallium module can draw transparent
graphs and text on top of what apps
On 03/22/2013 05:50 PM, Marek Olšák wrote:
Hi everyone, one image is better than a thousand words:
http://people.freedesktop.org/~mareko/gallium-hud.png
So there you have it. This gallium module can draw transparent graphs and text on top of
what apps are rendering. By default, it can show fra
On 03/25/2013 04:59 AM, jupiter wrote:
Hi Brian,
On 3/22/13, Brian Paul wrote:
On 03/21/2013 03:51 AM, jupiter wrote:
Hi Brian,
On 3/21/13, Brian Paul wrote:
On 03/20/2013 04:07 AM, jupiter wrote:
Hi Brian,
On 3/19/13, Brian Paulwrote:
It is fair to say, if running llvm driver in m
https://bugs.freedesktop.org/show_bug.cgi?id=54557
Kalyan changed:
What|Removed |Added
CC||kondapallykal...@gmail.com
--
You are receivin
From: Christian König
Even when we have arrays it is possible for simplify_cmp
to work on temps, just not on arrays.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=62696
Signed-off-by: Christian König
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp |2 +-
1 file changed, 1 insertion(+
From: Christian König
Avoid creating arrays if we replace indirect addressing anyway.
Signed-off-by: Christian König
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/mesa/state_tracker/st_glsl_to_tgsi.cpp
b/src/mesa/s
Hi Brian,
On 3/22/13, Brian Paul wrote:
> On 03/21/2013 03:51 AM, jupiter wrote:
>> Hi Brian,
>>
>> On 3/21/13, Brian Paul wrote:
>>> On 03/20/2013 04:07 AM, jupiter wrote:
Hi Brian,
On 3/19/13, Brian Paul wrote:
>> It is fair to say, if running llvm driver in my local machi
Fixes various test fallout from 90b5a2425a on Pineview, which claims to
support ARB_internalformat_query but doesn't actually provide the
driverfunc.
That driver is still broken [GetInternalformativ will still segfault!]
but it was silly to be going through the sample count logic in the
nonmultisa
On Sat, Mar 23, 2013 at 01:48:44PM -0700, Kenneth Graunke wrote:
> On 03/19/2013 03:57 AM, Pohjolainen, Topi wrote:
> >On Mon, Mar 18, 2013 at 04:35:10PM -0700, Jordan Justen wrote:
> >>With this change we now support interface block arrays.
> >>For example, cases like this:
> >>
> >>out block_name
65 matches
Mail list logo