On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand wrote:
> ---
> src/mesa/drivers/dri/i965/brw_vec4.cpp | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_vec4.cpp
> b/src/mesa/drivers/dri/i965/brw_vec4.cpp
> index 155a550..02a00b3 100644
Reviewed-by: Jordan Justen
On 2016-03-18 00:41:08, Iago Toral Quiroga wrote:
> ---
> docs/envvars.html | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/docs/envvars.html b/docs/envvars.html
> index 06aa0ac..6b5511b 100644
> --- a/docs/envvars.html
> +++ b/docs/envvars.html
> @@ -163,6
---
src/mesa/state_tracker/st_cb_bitmap_shader.c | 45 +---
1 file changed, 8 insertions(+), 37 deletions(-)
diff --git a/src/mesa/state_tracker/st_cb_bitmap_shader.c
b/src/mesa/state_tracker/st_cb_bitmap_shader.c
index cddea36..88779bc 100644
--- a/src/mesa/state_tracker
On Wed, Mar 16, 2016 at 2:01 AM, Iago Toral wrote:
> On Wed, 2016-03-16 at 09:48 +0100, Samuel Iglesias Gonsálvez wrote:
> >
> > On 15/03/16 08:41, Iago Toral wrote:
> > > On Mon, 2016-03-14 at 17:33 -0700, Jason Ekstrand wrote:
> > [...]
> > >> + nir_alu_type type; + union { - uint32_t u;
https://bugs.freedesktop.org/show_bug.cgi?id=94522
--- Comment #14 from Pekka Paalanen ---
(In reply to Jose Fonseca from comment #13)
> I wonder if 0xa8ec01b0 is some sort of funky device memory, or if that
> device memory was destroyed before llvmpipe was done.
>
> After all this is SwapBuffer
On Thu, Mar 17, 2016 at 11:17 AM, Matt Turner wrote:
> On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand
> wrote:
> > ---
> > src/mesa/drivers/dri/i965/brw_vec4.cpp | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/src/mesa/drivers/dri/i965/brw_vec4.cpp
> b/src/mesa/drivers/dri/i965
https://bugs.freedesktop.org/show_bug.cgi?id=91556
--- Comment #12 from Pavan Yalamanchili ---
Is this patch going through into a future release?
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
This approach leads to the emitters needing to know about both global and
buffer, even though at that point, they are identical. I was thinking that
in the lowering logic, buffer would just get rewritten as global (with the
offset added), thus not needing any change to the emitters. What do you
thi
---
docs/envvars.html | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/envvars.html b/docs/envvars.html
index 06aa0ac..e21b7c1 100644
--- a/docs/envvars.html
+++ b/docs/envvars.html
@@ -163,6 +163,7 @@ See the Xlib software driver
page for details.
blorp - emit messages about the blor
On Thu, Mar 17, 2016 at 3:53 PM, dw kim wrote:
> Matt,
>
> I uploaded v2 patch with corrected commit message. Other than
> commit message, everything is still same. Can you please re-review
> it and merge it if there's no issue?
Pushed. Thanks!
___
mes
On Wed, Mar 16, 2016 at 12:12:58AM -0700, Kenneth Graunke wrote:
> Less boilerplate.
>
> Signed-off-by: Kenneth Graunke
> ---
> src/mesa/drivers/common/meta.c | 34
> -
> src/mesa/drivers/dri/i965/brw_meta_fast_clear.c | 14 +++---
> 2 files changed,
Hello everyone, I'd like to build mesa with address sanitizer to help
finding bugs ,
I''m using mesa-11.1.2 autogen.sh/configure with env
CFLAGS="-fsanitize=address" CXXFLAGS="-fsanitize=address"
LDFLAGS="-fsanitize=address"
and then make, but it failed when linking .libs/pipe_r300.so with lots
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Fri, Mar 4, 2016 at 5:43 AM, Andres Gomez wrote:
> Hi,
>
> as complementary work to the one done to "Add FP64 support to the i965
> shader backends" at:
> https://bugs.freedesktop.org/show_bug.cgi?id=92760
>
> I've been working to add piglit tests that would check the new features
> added by t
Am 09.03.2016 um 15:53 schrieb Marek Olšák:
On Wed, Mar 9, 2016 at 4:54 AM, Michel Dänzer wrote:
On 08.03.2016 21:21, Christian König wrote:
From: Christian König
Linear layout should work for all formats as well.
The hardware actually doesn't support linear e.g. for compressed formats
or d
Hi all,
I was wondering if anyone knows of or has seen a crash when Mesa is compiled
for with LVM Pipe ?
The reason I ask is that if our user uses a compiled version of Mesa using the
slower software render, it works fine, the moment we compile it with LVM, it
crashes.
I have an api trace that
No shader-db change on Haswell
---
src/mesa/drivers/dri/i965/brw_vec4.cpp | 40 +-
1 file changed, 10 insertions(+), 30 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vec4.cpp
b/src/mesa/drivers/dri/i965/brw_vec4.cpp
index 02a00b3..0a11991 100644
--- a/sr
On Mar 17, 2016 8:27 PM, "Matt Turner" wrote:
>
> On Thu, Mar 17, 2016 at 5:17 PM, Pierre Moreau
wrote:
> > This fixes a compile error while building Nouveau with C++11 enabled
(and
> > glibc >= 2.23). This happens if SWR is enabled, as it forces C++11.
>
> That seems bad, right?
>
> Enabling Ope
Previously, the GLSL compiler successfully parsed the "invariant" and
"precise" keywords and set bits on the variables, but we never did anything
with them. This series adds code to propagate "invariant" and "precise"
all the way thorugh NIR and bail in unsafe optimizations if we see it. The
GLSL
---
src/compiler/glsl/opt_algebraic.cpp | 16
1 file changed, 16 insertions(+)
diff --git a/src/compiler/glsl/opt_algebraic.cpp
b/src/compiler/glsl/opt_algebraic.cpp
index 1e58062..2fea240 100644
--- a/src/compiler/glsl/opt_algebraic.cpp
+++ b/src/compiler/glsl/opt_algebraic.cpp
---
src/compiler/nir/nir_search.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/compiler/nir/nir_search.c b/src/compiler/nir/nir_search.c
index 56d7e81..4cb2d4d 100644
--- a/src/compiler/nir/nir_search.c
+++ b/src/compiler/nir/nir_search.c
@@ -246,7 +246,7 @@ mat
---
src/mesa/drivers/dri/i965/brw_fs.cpp | 74 +---
1 file changed, 18 insertions(+), 56 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs.cpp
b/src/mesa/drivers/dri/i965/brw_fs.cpp
index 365231e..9f303d5 100644
--- a/src/mesa/drivers/dri/i965/brw_fs.cpp
On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand wrote:
> NIR already has this optimization and it can do much better than the little
> peephole in the backend.
>
> No shader-db change on Broadwell.
> ---
> src/mesa/drivers/dri/i965/brw_fs.cpp | 11 ---
> 1 file changed, 11 deletions(-)
>
Acked-by: Pierre Moreau
On 09:55 PM - Mar 15 2016, Samuel Pitoiset wrote:
> Having two different variables for the driver constant buffer slot
> is confusing and really useless.
>
> Signed-off-by: Samuel Pitoiset
> ---
> src/gallium/drivers/nouveau/codegen/nv50_ir_driver.h | 3 +--
>
Reviewed-by: Jordan Justen
On 2016-03-14 15:00:06, Kenneth Graunke wrote:
> Thanks to James Legg for finding this!
>
> From the ARB_tessellation_shader spec:
> "The number of isolines generated is derived from the first outer
> tessellation level; the number of segments in each isoline is
> de
---
src/compiler/nir/nir_instr_set.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/src/compiler/nir/nir_instr_set.c b/src/compiler/nir/nir_instr_set.c
index 159ded0..00e4784 100644
--- a/src/compiler/nir/nir_instr_set.c
+++ b/src/compiler/nir/nir_instr_set.c
NIR already has this optimization and it can do much better than the little
peephole in the backend.
No shader-db change on Broadwell.
---
src/mesa/drivers/dri/i965/brw_fs.cpp | 11 ---
1 file changed, 11 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs.cpp
b/src/mesa/drivers/
On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand
wrote:
> This little series prepares the backend compiler for invariant and precise
> by removing any potentially unsafe optimizations. The easiest
> implementation for invariant and precise seems to be the same: Don't change
> the semantics of in
The FS backend bails as well.
---
src/mesa/drivers/dri/i965/brw_vec4_copy_propagation.cpp | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/brw_vec4_copy_propagation.cpp
b/src/mesa/drivers/dri/i965/brw_vec4_copy_propagation.cpp
index 92423e1..2dfe623 100644
--- a/sr
On 16/03/16 19:33, Kenneth Graunke wrote:
The SIN and COS instructions on Intel hardware can produce values
slightly outside of the [-1.0, 1.0] range for a small set of values.
Obviously, this can break everyone's expectations about trig functions.
According to an internal presentation, the COS
This little series prepares the backend compiler for invariant and precise
by removing any potentially unsafe optimizations. The easiest
implementation for invariant and precise seems to be the same: Don't change
the semantics of invariant or precise values. This means that we need to
track what
On Thu, Mar 17, 2016 at 6:14 PM, Timothy Arceri
wrote:
> The function has only one user and strings are always null terminated.
> ---
> src/mesa/program/ir_to_mesa.cpp | 2 +-
> src/mesa/program/prog_parameter.c | 38 --
> src/mesa/program/prog_parameter.h |
Series is
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Thu, Mar 17, 2016 at 10:45 AM, Matt Turner wrote:
> On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand
> wrote:
> > NIR already has this optimization and it can do much better than the
> little
> > peephole in the backend.
> >
> > No shader-db change on Broadwell.
> > ---
> > src/mesa/drivers/
---
src/compiler/nir/nir.h | 11 +++
src/compiler/nir/nir_clone.c | 1 +
src/compiler/nir/nir_print.c | 2 ++
3 files changed, 14 insertions(+)
diff --git a/src/compiler/nir/nir.h b/src/compiler/nir/nir.h
index 34f31eb..94b981b 100644
--- a/src/compiler/nir/nir.h
+++ b/src/compile
Add support for OpenCL global memory buffers, note this has only
been tested with regular load and stores and likely needs more work
for e.g. atomic ops.
Signed-off-by: Hans de Goede
---
Changes in v2:
-Redo on top of new "Use FILE_MEMORY_BUFFER for buffers" patch
---
src/gallium/drivers/nouveau
For the first basic block in the program 'block->prev()' would return
an incorrectly cast list head sentinel and the subsequent
'prev_block->end()' dereference would read invalid memory. Introduced
in c7deee69ea6f64ea5b563985bf19d9deebe73b5b.
CC: Ian Romanick
---
src/mesa/drivers/dri/i965/brw_d
Currently mesa fails building with the x32 abi as ms_abi is not defined
in such a case.
The patch uses ms_abi only for amd64 targets and stdcall only for i386
targets to be sure that those are defined.
This patch additionally checks for __GNUC__ to guarantee that
__attribute__ is available.
---
On Thu, Mar 17, 2016 at 5:17 PM, Pierre Moreau wrote:
> This fixes a compile error while building Nouveau with C++11 enabled (and
> glibc >= 2.23). This happens if SWR is enabled, as it forces C++11.
That seems bad, right?
Enabling OpenSWR should affect how any other drivers are built. Why
does
Am 17.03.2016 um 01:52 schrieb Jason Anderssen:
> Hi all,
>
> I was wondering if anyone knows of or has seen a crash when Mesa is
> compiled for with LVM Pipe ?
> The reason I ask is that if our user uses a compiled version of Mesa
> using the slower software render, it works fine, the moment we c
From: Nicolai Hähnle
v2: new signature style for buffer intrinsics
---
I want to change the signature for buffer intrinsics while it is still
feasible to do so; the only difference with v1 is two lines that are removed
in buffer_append_args, but you'll need a new version of LLVM, which I've
pushe
Reformat code. Improve assertion.
---
src/mesa/state_tracker/st_mesa_to_tgsi.c | 69
1 file changed, 44 insertions(+), 25 deletions(-)
diff --git a/src/mesa/state_tracker/st_mesa_to_tgsi.c
b/src/mesa/state_tracker/st_mesa_to_tgsi.c
index 8772efb..8a12ce4 100644
On Thu, Mar 17, 2016 at 11:55 AM, Matt Turner wrote:
> On Thu, Mar 17, 2016 at 11:52 AM, Jason Ekstrand
> wrote:
> >
> >
> > On Thu, Mar 17, 2016 at 11:18 AM, Matt Turner
> wrote:
> >>
> >> On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand
> >> wrote:
> >> > ---
> >> > src/mesa/drivers/dri/i96
On Thu, Mar 17, 2016 at 4:42 PM, Jordan Justen
wrote:
> On 2016-03-17 01:04:27, Kenneth Graunke wrote:
> > Yuanhan Liu decided these were useful for linear filtering in
> > commit 76669381 (circa 2011). Prior to that, we never set them;
> > it seems he tried to preserve that behavior for nearest
Matt Turner writes:
> On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand wrote:
>> Shader-db results on Broadwell:
>>
>> total instructions in shared programs: 7517815 -> 7517816 (0.00%)
>> instructions in affected programs: 46 -> 47 (2.17%)
>> HURT: 1
>>
>> Th
Hi,
This is probably a very simple question I hope, using scons, what is the
easiest way to create a debug build, the Doc on the website I think only refers
to Make-Config ?
I am also cross compiling for windows.
Cheers and thanks again in advance.
Jason
Internet Email Confidentiality Footer: T
---
src/mesa/program/prog_parameter.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/src/mesa/program/prog_parameter.c
b/src/mesa/program/prog_parameter.c
index 470c98e..02d84f2 100644
--- a/src/mesa/program/prog_parameter.c
+++ b/src/mesa/program/prog_parame
On Thu, Mar 17, 2016 at 6:10 PM, Matt Turner wrote:
> On Thu, Mar 17, 2016 at 5:51 PM, Jason Ekstrand
> wrote:
> > ---
> > src/compiler/nir/nir.h | 11 +++
> > src/compiler/nir/nir_clone.c | 1 +
> > src/compiler/nir/nir_print.c | 2 ++
> > 3 files changed, 14 insertions(+)
> >
These magic file-index defines where only ever used in the nouveau code
and that no longer uses them.
Signed-off-by: Hans de Goede
---
Changes in v2:
-Split out of "nouveau: codegen: Disable more old resource handling code"
---
src/gallium/include/pipe/p_shader_tokens.h | 9 -
1 file cha
For the series:
Reviewed-by: Charmaine Lee
From: Brian Paul
Sent: Wednesday, March 16, 2016 5:43 PM
To: mesa-dev@lists.freedesktop.org
Cc: Charmaine Lee
Subject: [PATCH 4/4] st/mesa: clean up st_translate_texture_target()
Reformat code. Improve assertio
We had a number of last-minute nominations and this did not give all nominees
the chance to respond to the nominations. Hence, we are extending the
nomination period for two weeks. All election dates thus move back by two
weeks. Below is the original text of the nomination request email.
We are s
---
src/mesa/program/prog_parameter.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/src/mesa/program/prog_parameter.h
b/src/mesa/program/prog_parameter.h
index c04d7a2..acc5b6c 100644
--- a/src/mesa/program/prog_parameter.h
+++ b/src/mesa/program/prog_parameter.h
@@ -99,12 +99,6 @@ _me
Edward O'Callaghan wrote on 19.03.2016 07:41:
> Signed-off-by: Edward O'Callaghan
> ---
> docs/GL3.txt | 2 +-
> docs/relnotes/11.3.0.html | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/docs/GL3.txt b/docs/GL3.txt
> index 3058996..b9fc86b 100644
> --- a/do
Hi Nicolai,
This series is,
Reviewed-by: Edward O'Callaghan
Thanks,
On 2016-03-19 14:37, Nicolai Hähnle wrote:
Hi,
these patches apply on top of my ARB_shader_image_load_store series.
Together,
they fix a few remaining fails with piglit's
arb_shader_image_load_store-host-mem-barrier.
You c
On Thu, Mar 17, 2016 at 12:47 PM, Nicolai Hähnle wrote:
> On 16.03.2016 19:43, Brian Paul wrote:
>>
>> The return type is float, which is what was implicitly used before,
>> AFAICT.
>
>
> Isn't this technically incorrect when the uploaded texture is integer?
>
> To be honest, it's not really clear
On 2016-03-19 21:08, Kai Wasserbäch wrote:
Edward O'Callaghan wrote on 19.03.2016 07:41:
Signed-off-by: Edward O'Callaghan
---
docs/GL3.txt | 2 +-
docs/relnotes/11.3.0.html | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index 3058
Jason Ekstrand writes:
> ---
> src/compiler/nir/glsl_to_nir.cpp | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/compiler/nir/glsl_to_nir.cpp
> b/src/compiler/nir/glsl_to_nir.cpp
> index 613b138..f592c57 100644
> --- a/src/compiler/nir/glsl_to_nir.cpp
> +++ b/src/compiler/nir/glsl
This code predates me. I can't believe it's been useful for a long time.
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On 17.03.2016 11:50, Ilia Mirkin wrote:
On Thu, Mar 17, 2016 at 12:47 PM, Nicolai Hähnle wrote:
On 16.03.2016 19:43, Brian Paul wrote:
The return type is float, which is what was implicitly used before,
AFAICT.
Isn't this technically incorrect when the uploaded texture is integer?
To be h
According to the OpenGL ES 3.2 spec's description of GenerateMipmap:
"An INVALID_OPERATION error is generated if the levelbase array was not
specified with an unsized internal format from table 8.3 or a sized
internal format that is both color-renderable and texture-filterable
according to tabl
Fixes compilation error since 5aea0d691.
---
src/gallium/drivers/r300/r300_texture.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r300/r300_texture.c
b/src/gallium/drivers/r300/r300_texture.c
index 22a613f..709345a 100644
--- a/src/gallium/drivers/r300/r
---
src/gallium/auxiliary/tgsi/tgsi_transform.h | 34 +
1 file changed, 34 insertions(+)
diff --git a/src/gallium/auxiliary/tgsi/tgsi_transform.h
b/src/gallium/auxiliary/tgsi/tgsi_transform.h
index 27e6179..4dd7dda 100644
--- a/src/gallium/auxiliary/tgsi/tgsi_transfor
On Thursday, March 17, 2016 6:18:39 PM PDT Martin Peres wrote:
> On 16/03/16 19:33, Kenneth Graunke wrote:
> > The SIN and COS instructions on Intel hardware can produce values
> > slightly outside of the [-1.0, 1.0] range for a small set of values.
> > Obviously, this can break everyone's expectat
Ping
On Fri, Mar 11, 2016 at 4:01 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> Cons:
> - it was only integrated in r600g
> - it doesn't work with GPUVM
> - it records buffer contents at the end of IBs instead of at the beginning,
> so the replay isn't exact
> - it lacks an IB parser and user
Acked-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Stencil texturing is required by ES 3.1. Apparently we never actually
turned it on, and we missed some necessary code.
Fixes nine dEQP-GLES31.functional tests:
stencil_texturing.format.stencil_index8_2d
texture.border_clamp.formats.stencil_index8.nearest_size_pot
texture.border_clamp.formats.ste
On Thu, Mar 17, 2016 at 11:18 AM, Matt Turner wrote:
> On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand
> wrote:
> > ---
> > src/mesa/drivers/dri/i965/brw_vec4.cpp | 8 +++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/src/mesa/drivers/dri/i965/brw_vec4.cpp
> b/sr
Instead make use of constants to improve readability.
The first 32 bytes of the driver constant buffer are unknown... This
doesn't seem to be used in the codegen part, but if the texBindBase
offset is shifted from 0x20 to 0x00, this breaks the universe for
really weird reasons. This sounds like to
The return type is float, which is what was implicitly used before, AFAICT.
---
src/mesa/state_tracker/st_cb_texture.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/mesa/state_tracker/st_cb_texture.c
b/src/mesa/state_tracker/st_cb_texture.c
index bffa4d0..6ee55c6 100644
--- a/src/
From: Nicolai Hähnle
Aside from the bug below, it fixes a simplistic test I've written locally,
and I see no regression in Piglit for radeonsi.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94595
Cc: mesa-sta...@lists.freedesktop.org
---
src/mesa/state_tracker/st_cb_fbo.c | 22
On 03/16/2016 09:57 PM, Jordan Justen wrote:
The OpenGLES GLSL 3.1 and OpenGL GLSL 4.3 specifications both remove
the requirement for the output and input interpolation qualifiers to
match.
Note: I'm changing desktop OpenGL to allow the interpolation to
differ, starting with 4.3, whereas the co
We should check whether check_explicit_uniform_locations has
failed before we pass the number of explicit uniform locations
to link_assign_uniform_locations.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94549#c3
---
src/compiler/glsl/linker.cpp | 7 ++-
1 file changed, 6 insertions(
From: Nishanth Peethambaran
Attach the timestamp to the dpb buffer and use that timestamp
while pushing buffer from dpb list to the omx client.
Reviewed-by: Christian König
Signed-off-by: Nishanth Peethambaran
Cc: "11.1 11.2"
---
src/gallium/state_trackers/omx/vid_dec.c| 11 +
---
docs/envvars.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/envvars.html b/docs/envvars.html
index 06aa0ac..6b5511b 100644
--- a/docs/envvars.html
+++ b/docs/envvars.html
@@ -163,6 +163,8 @@ See the Xlib software driver
page for details.
blorp - emit messages about the bl
I suspect you simply ran into an issue with old mesa and new llvm.
Unfortunately some usage of the c++ abi of llvm is unavoidable, and the
abi is unstable, thus breaking quite often. And we do not generally
backport such fixes to older mesa releases (if only mostly because
nobodoy would actually te
On 2016-03-17 01:04:27, Kenneth Graunke wrote:
> Yuanhan Liu decided these were useful for linear filtering in
> commit 76669381 (circa 2011). Prior to that, we never set them;
> it seems he tried to preserve that behavior for nearest filtering.
>
> It turns out they're useful for nearest filteri
On 06:34 PM - Mar 18 2016, Vinson Lee wrote:
> Fix clang build error.
>
> CXX codegen/nv50_ir_lowering_nvc0.lo
> codegen/nv50_ir_lowering_nvc0.cpp:1783:42: error: invalid suffix 'd' on
> floating constant
> Value *zero = bld.loadImm(NULL, 0.0d);
>
On Thu, Mar 17, 2016 at 11:52 AM, Jason Ekstrand wrote:
>
>
> On Thu, Mar 17, 2016 at 11:18 AM, Matt Turner wrote:
>>
>> On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand
>> wrote:
>> > ---
>> > src/mesa/drivers/dri/i965/brw_vec4.cpp | 8 +++-
>> > 1 file changed, 7 insertions(+), 1 deletion
Functions arguments get a definition from the function itself, a definition
which is therefore not linked to any instruction. If a value ends up having a
definition but no linked instruction, the register allocation pass doesn't
need to consider that value.
This fixes a null pointer dereference du
On 03/16/2016 11:17 AM, Samuel Pitoiset wrote:
The offsets are wrong in this patch... But even after fixing them I have
a few number of regressions (~10 piglit tests). Anyway, these changes
are not too useful for now, so I'm going to get rid of it.
I'll now try with Kepler.
Confirmed, no reg
Jason Ekstrand writes:
> ---
> src/compiler/nir/nir.h | 11 +++
> src/compiler/nir/nir_clone.c | 1 +
> src/compiler/nir/nir_print.c | 2 ++
> 3 files changed, 14 insertions(+)
>
> diff --git a/src/compiler/nir/nir.h b/src/compiler/nir/nir.h
> index 34f31eb..94b981b 100644
> ---
Jason Ekstrand writes:
> ---
> src/compiler/nir/nir_lower_alu_to_scalar.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/compiler/nir/nir_lower_alu_to_scalar.c
> b/src/compiler/nir/nir_lower_alu_to_scalar.c
> index 312d2f9..082242e 100644
> --- a/src/compiler/nir/nir_lower_alu_to_
From: Nishanth Peethambaran
Reviewed-by: Christian König
Signed-off-by: Nishanth Peethambaran
Cc: "11.1 11.2"
---
src/gallium/state_trackers/omx/vid_dec.c | 10 +++---
src/gallium/state_trackers/omx/vid_dec_h264.c | 8 ++---
src/gallium/state_trackers/omx/vid_enc.c | 44 +++
---
src/compiler/Makefile.sources | 1 +
src/compiler/glsl/glsl_parser_extras.cpp | 1 +
src/compiler/glsl/ir_optimization.h| 1 +
src/compiler/glsl/propagate_invariance.cpp | 125 +
4 files changed, 128 insertions(+)
create mode 100644 src
On Wed, Feb 24, 2016 at 10:02 PM, Connor Abbott wrote:
> I believe this is correct, and won't cause any issues with phi node
> placement, etc. before dead_cf comes and gets rid any code in the
> unreachable block(s).
>
> Reviewed-by: Connor Abbott
>
> BTW, I'd ask that you hold off on pushing th
On 03/18/2016 04:41 PM, Plamena Manolova wrote:
We should check whether check_explicit_uniform_locations has
failed before we pass the number of explicit uniform locations
to link_assign_uniform_locations.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94549#c3
---
src/compiler/glsl/li
Instead of hard-coded 2D tex target in tgsi_transform_tex_2d_inst()
---
src/gallium/auxiliary/draw/draw_pipe_aaline.c| 10 +-
src/gallium/auxiliary/tgsi/tgsi_transform.h | 17 ++---
src/gallium/auxiliary/util/u_pstipple.c | 10 +-
src/mesa/state_tracke
Reviewed-by: Jordan Justen
On 2016-03-15 00:49:47, Kenneth Graunke wrote:
> According to the ES 3.0 and GL 4.4 specifications, glBlitFramebuffer
> is supposed to perform sRGB decoding and encoding whenever sRGB formats
> are in use. The ES 3.0 specification is completely clear, and has
> always
On Mar 19, 2016 8:44 AM, "Pierre Moreau" wrote:
>
> On 06:34 PM - Mar 18 2016, Vinson Lee wrote:
> > Fix clang build error.
> >
> > CXX codegen/nv50_ir_lowering_nvc0.lo
> > codegen/nv50_ir_lowering_nvc0.cpp:1783:42: error: invalid suffix 'd' on
floating constant
> > Value *zero = bld.
Why not derive this information from is_format_supported with rgba8 format?
Seems like that would do the trick. Look at how the st already does
something similar in st_extensions.c iirc.
Your scheme only enables power-of-two msaa levels, and is redundant wrt the
function I mentioned earlier...
As
On Wed, Mar 16, 2016 at 07:25:56PM -0700, Kenneth Graunke wrote:
> Stencil texturing is required by ES 3.1. Apparently we never actually
> turned it on, and we missed some necessary code.
>
> Fixes nine dEQP-GLES31.functional tests:
>
> stencil_texturing.format.stencil_index8_2d
> texture.border
On Thu, Mar 17, 2016 at 5:51 PM, Jason Ekstrand wrote:
> ---
> src/compiler/nir/nir_builder.h | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/src/compiler/nir/nir_builder.h b/src/compiler/nir/nir_builder.h
> index d546e41..1d61ff9 100644
> --- a/src/compiler/nir/nir_builder.h
>
---
src/mesa/state_tracker/st_mesa_to_tgsi.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/src/mesa/state_tracker/st_mesa_to_tgsi.c
b/src/mesa/state_tracker/st_mesa_to_tgsi.c
index 8a12ce4..7a686b1 100644
--- a/src/mesa/state_tracker/st_mesa_to_tgsi.c
+++ b/src/mesa/
In June 2015, Rob Clark started updating the tgsi utility code to emit
SVIEW declarations in various shaders (for polygon stipple, blitting,
etc). These patches do the same for the Mesa state tracker.
The VMware driver will use this.
---
src/mesa/state_tracker/st_cb_bitmap_shader.c | 4
1 f
On Sat, Mar 19, 2016 at 7:41 AM, Edward O'Callaghan
wrote:
> Signed-off-by: Edward O'Callaghan
> ---
> src/gallium/drivers/radeonsi/si_pipe.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/src/gallium/drivers/radeonsi/si_pipe.c
> b/src/gallium/drivers/radeonsi/si_pi
That would limit us to supporting sample counts for which we have
texture formats.
As far as I understand with radeonsi we can support 16 samples without
any attachments, but all formats are limited to <= 8 samples.
- Bas
On Sat, Mar 19, 2016 at 3:00 PM, Ilia Mirkin wrote:
> Why not derive this
On Sat, Mar 19, 2016 at 11:14 AM, Bas Nieuwenhuizen
wrote:
> That would limit us to supporting sample counts for which we have
> texture formats.
>
> As far as I understand with radeonsi we can support 16 samples without
> any attachments, but all formats are limited to <= 8 samples.
So you're go
On Sat, Mar 19, 2016 at 2:41 AM, Edward O'Callaghan
wrote:
> Signed-off-by: Edward O'Callaghan
> ---
> src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_screen.c
> b/src/gallium/driver
https://bugs.freedesktop.org/show_bug.cgi?id=94522
--- Comment #15 from comicfans44 ---
(In reply to Pekka Paalanen from comment #14)
> (In reply to Jose Fonseca from comment #13)
> > I wonder if 0xa8ec01b0 is some sort of funky device memory, or if that
> > device memory was destroyed before llv
On Thu, Mar 17, 2016 at 10:21 AM, Jason Ekstrand wrote:
> Shader-db results on Broadwell:
>
> total instructions in shared programs: 7517815 -> 7517816 (0.00%)
> instructions in affected programs: 46 -> 47 (2.17%)
> HURT: 1
>
> The one hurt shader is a shader f
1 - 100 of 205 matches
Mail list logo
