This is ok. It can still break if multiple stages contain different
streamout info, which might happen with separate shader objects.
Marek
On Mon, Nov 19, 2018, 1:56 AM Gert Wollny From: Gert Wollny
>
> With 5d517a streamout info is only attached to the shader for which the
> transform feedback
On Mon, Nov 19, 2018 at 08:17:32AM +0100, Luc Verhaegen wrote:
> Hi,
>
> At FOSDEM on saturday the 3rd of february 2018, there will be another
> graphics DevRoom. URL: https://fosdem.org/2018/
That should of course read:
At FOSDEM on saturday the 2nd of february 2019, there will be another
graph
Hi,
At FOSDEM on saturday the 3rd of february 2018, there will be another
graphics DevRoom. URL: https://fosdem.org/2018/
The focus of this DevRoom is of course the same as the previous
editions, namely:
* Graphics drivers: from display to media to 3d drivers, both in kernel
or userspace. Be
On Mon, 19 Nov 2018 at 16:56, Gert Wollny wrote:
>
> From: Gert Wollny
>
> With 5d517a streamout info is only attached to the shader for which the
> transform feedback is actually recorded, but the driver set the context info
> with each state submitted, thereby always using the info data that wa
From: Gert Wollny
With 5d517a streamout info is only attached to the shader for which the
transform feedback is actually recorded, but the driver set the context info
with each state submitted, thereby always using the info data that was
attached to the vertex shader.
Pass the streamout strid
Here we rework force_unroll_array_access() so that we can reused
the induction variable detection in a following patch.
---
src/compiler/nir/nir_loop_analyze.c | 49 -
1 file changed, 35 insertions(+), 14 deletions(-)
diff --git a/src/compiler/nir/nir_loop_analyze.c
b
This adds partial loop unrolling support and makes use of a
guessed trip count based on array access.
The code is written so that we could use partial unrolling
more generally, but for now it's only use when we have guessed
the trip count.
We use partial unrolling for this guessed trip count beca
---
src/compiler/nir/nir_control_flow.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/compiler/nir/nir_control_flow.h
b/src/compiler/nir/nir_control_flow.h
index 2ea460e5df..9111b30a29 100644
--- a/src/compiler/nir/nir_control_flow.h
+++ b/src/compiler/nir/nir_control_flow.h
---
src/compiler/nir/nir_opt_loop_unroll.c | 116 ++---
1 file changed, 64 insertions(+), 52 deletions(-)
diff --git a/src/compiler/nir/nir_opt_loop_unroll.c
b/src/compiler/nir/nir_opt_loop_unroll.c
index a25a89f094..d9272fedd8 100644
--- a/src/compiler/nir/nir_opt_loop_unrol
This series add support for partial loop unrolling for loops with an
unknown trip count. The new partial_unroll function allows the caller
to specifiy how may times the loop should be unrolled and then the
loop is inserted in the innermost continue branch of the unrolled loop.
For now we only do p
---
src/compiler/nir/nir_opt_loop_unroll.c | 74 ++
1 file changed, 28 insertions(+), 46 deletions(-)
diff --git a/src/compiler/nir/nir_opt_loop_unroll.c
b/src/compiler/nir/nir_opt_loop_unroll.c
index ea2012e292..a25a89f094 100644
--- a/src/compiler/nir/nir_opt_loop_unrol
This detects an induction variable used as an array index to guess
the trip count of the loop. This enables us to do a partial
unroll of the loop, with can eventually result in the loop being
eliminated.
---
src/compiler/nir/nir.h | 4 ++
src/compiler/nir/nir_loop_analyze.c | 78
In order to stop continuously partially unrolling the same loop
we add the bool partialy_unrolled to nir_loop, we add it here
rather than in nir_loop_info because nir_loop_info is only set
via loop analysis and is intended to be cleared before each
analysis. Also nir_loop_info is never cloned.
---
---
src/compiler/nir/nir_loop_analyze.c | 31 ++---
1 file changed, 10 insertions(+), 21 deletions(-)
diff --git a/src/compiler/nir/nir_loop_analyze.c
b/src/compiler/nir/nir_loop_analyze.c
index 9c3fd2f286..c779383b36 100644
--- a/src/compiler/nir/nir_loop_analyze.c
+++ b
From: Dave Airlie
The in_fence_fd needs to be initialised to -1.
Fixes: d1a1c21e7 (virgl: native fence fd support)
---
src/gallium/winsys/virgl/vtest/virgl_vtest_winsys.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/winsys/virgl/vtest/virgl_vtest_winsys.c
b/src/gallium/winsy
https://bugs.freedesktop.org/show_bug.cgi?id=107991
--- Comment #16 from kyle.de...@mykolab.com ---
Well, not quite.
John, from above, is still having issues, apparently, so I'm happy to wait.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for t
From: Dave Airlie
I've no idea how right or wrong this is, it stops a crash with
dEQP-VK.spirv_assembly.instruction.compute.variable_pointers.compute.workgroup_two_buffers
on radv with variablePointers.
---
src/compiler/nir/nir_deref.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/
These 3 I think I've sent before, I've cleaned them up a bit, and
hopefully taken any review into account.
These are enough to get variablepointers on radv to work, but they
are the easiest ones to review first.
Dave.
___
mesa-dev mailing list
mesa-de
From: Dave Airlie
Check if the base ends up with no variable, and continue
if we see that case outside the loop.
---
src/compiler/nir/nir_lower_indirect_derefs.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/compiler/nir/nir_lower_indirect_derefs.c
b/src/compiler/nir/nir_lower_ind
From: Dave Airlie
---
src/compiler/spirv/spirv_to_nir.c | 15 ---
src/compiler/spirv/vtn_variables.c | 3 ++-
2 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/src/compiler/spirv/spirv_to_nir.c
b/src/compiler/spirv/spirv_to_nir.c
index 4fa02b6fd7b..a05c4d236ca 100644
From: Dave Airlie
I posted a load of hacks before to do this, Jason suggested this,
just check the deref mode, not the variable mode and delay getting
the variable until we know the type.
avoids crashes when derefing shared memory pointers.
---
src/compiler/nir/nir_gather_info.c | 7 +++
1
https://bugs.freedesktop.org/show_bug.cgi?id=107991
--- Comment #15 from Rob Stolarz ---
I too am no longer seeing crashes on any apitrace file here or from the
savestate, as of linux 4.19.2 / mesa 19.0.0_devel.105705.b4380cb070. Kyle,
would you agree that this is resolved?
--
You are receiving
If the user specifies --enable-foo; we should be failing with an error
if we can't find the dependencies for foo. Currently however, we're just
disabling foo regardless of whether or not the user explicitly asked for
it. So, fix that
Signed-off-by: Lyude Paul
---
configure.ac | 50 ++
The series looks great. Just a few minor things below.
Reviewed-by: Brian Paul
On 11/17/2018 05:14 AM, mathias.froehl...@gmx.net wrote:
> From: Mathias Fröhlich
>
> Factor out struct gl_vertex_format from array attributes.
> The data type is supposed to describe the type of a vertex
> elemen
That file can live anywhere and can be referenced by absolute path.
On November 17, 2018 9:15:20 AM PST, "Kai Wasserbäch"
wrote:
>Hey Dylan,
>Dylan Baker wrote on 17.11.18 05:04:
>> Quoting Dylan Baker (2018-09-17 09:44:07)
>>> I feel like for !windows meson is in good enough shape at this point
Eric Engestrom writes:
> Fixes: d971a4230d54069c996bc "loader: Factor out the common driver
> opening logic from each loader."
> Cc: Eric Anholt
> Signed-off-by: Eric Engestrom
Reviewed-by: Eric Anholt
signature.asc
Description: PGP signature
__
Fixes: d971a4230d54069c996bc "loader: Factor out the common driver
opening logic from each loader."
Cc: Eric Anholt
Signed-off-by: Eric Engestrom
---
src/gbm/backends/dri/gbm_dri.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gbm/backends/
Am Freitag, den 16.11.2018, 20:04 -0800 schrieb Dylan Baker:
>
> Is there anything else we're missing in meson to be able to drop
> autotools?
One thing that I notes is that it seems to be impossible to run the
test suite for just one subdirectory because the only way to run the
build is from the
28 matches
Mail list logo
