Hi,
On 07-09-15 21:55, Ilia Mirkin wrote:
May I ask why you're doing 512x512 instead of 1024x1024? These are
already scaled up coordinates, so 1024x1024 should work no? Or is it
because of the seams on the edges? Do those not also appear with
512x512 or does it sample outside of the box?
This
On Monday, September 07, 2015 10:51:37 AM Jason Ekstrand wrote:
> On Sep 3, 2015 1:49 AM, "Kenneth Graunke" wrote:
> >
> > This patch also introduces a lowering pass to convert the simple GS
> > intrinsics to the new ones. See the comments above that for the
> > rationale
On Tuesday, September 08, 2015 08:15:11 AM Tapani Pälli wrote:
> I did not get as impressive results with these 3 patches (how did you
> measure?) but on my machine (HSW GT2) complete shader_runner time goes
> from ~83 secs to ~70secs so it is definitely improving.
>
> I simply do 'time
Hi,
On 07-09-15 22:00, Ilia Mirkin wrote:
On Mon, Sep 7, 2015 at 3:50 PM, Hans de Goede wrote:
msaa use on nv30 may trigger a (mesa?) bug where dmesg says:
[ 1197.850642] nouveau E[soffice.bin[3785]] fail ttm_validate
[ 1197.850648] nouveau E[soffice.bin[3785]]
On 8 September 2015 at 18:00, Hans de Goede wrote:
> Hi,
>
> On 07-09-15 22:00, Ilia Mirkin wrote:
>>
>> On Mon, Sep 7, 2015 at 3:50 PM, Hans de Goede wrote:
>>>
>>> msaa use on nv30 may trigger a (mesa?) bug where dmesg says:
>>> [ 1197.850642]
On 07.09.2015 07:14, Marek Olšák wrote:
> From: Marek Olšák
>
> This allows using the new tex instrinsics unconditionally.
The series is
Reviewed-by: Michel Dänzer
--
Earthling Michel Dänzer | http://www.amd.com
Libre
On 07.09.2015 09:15, Dave Airlie wrote:
> On 7 September 2015 at 08:17, Marek Olšák wrote:
>> From: Marek Olšák
>>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91881
>
> Might be nice to say where the regression happened in the commit, and
>
https://bugs.freedesktop.org/show_bug.cgi?id=91888
Daniel Stone changed:
What|Removed |Added
Status|NEW |RESOLVED
On Monday, September 07, 2015 11:06:54 AM Jason Ekstrand wrote:
> On Thu, Sep 3, 2015 at 1:48 AM, Kenneth Graunke wrote:
> > By performing the vertex counting in NIR, we're able to elide a ton of
> > useless safety checks around every EmitVertex() call:
> >
> > total
On 09/08/2015 12:34 PM, Kenneth Graunke wrote:
On Tuesday, September 08, 2015 08:15:11 AM Tapani Pälli wrote:
I did not get as impressive results with these 3 patches (how did you
measure?) but on my machine (HSW GT2) complete shader_runner time goes
from ~83 secs to ~70secs so it is
mesa/src/mesa/program/prog_to_nir.c: In function
'setup_registers_and_variables':
/mesa/src/mesa/program/prog_to_nir.c:1059:22: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < c->prog->NumTemporaries; i++) {
^
mesa/src/mesa/drivers/dri/i965/brw_eu_compact.c: In function
'set_3src_control_index':
mesa/src/mesa/drivers/dri/i965/brw_eu_compact.c:805:22: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < ARRAY_SIZE(gen8_3src_control_index_table);
mesa/src/glsl/nir/nir_lower_tex_projector.c: In function
'nir_lower_tex_projector_block':
mesa/src/glsl/nir/nir_lower_tex_projector.c:63:25: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < tex->num_srcs; i++) {
mesa/src/mesa/drivers/dri/i965/intel_mipmap_tree.c: In function
'intel_miptree_alloc_hiz':
mesa/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1771:44: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (int level = mt->first_level; level <=
mesa/src/mesa/drivers/dri/i965/brw_state_dump.c: In function
'dump_sampler_state':
mesa/src/mesa/drivers/dri/i965/brw_state_dump.c:382:18: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (i = 0; i < size / 16; i++) {
^
mesa/src/mesa/drivers/dri/i965/intel_mipmap_tree.c: In function
'intel_gen7_hiz_buf_create':
mesa/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1544:47: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (int level = mt->first_level; level <=
mesa/src/mesa/drivers/dri/i965/intel_mipmap_tree.c: In function
'intel_gen8_hiz_buf_create':
mesa/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1638:44: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (int level = mt->first_level; level <=
mesa/src/glsl/nir/nir_opt_peephole_ffma.c: In function 'get_mul_for_src':
mesa/src/glsl/nir/nir_opt_peephole_ffma.c:130:27: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (unsigned i = 0; i < num_components; i++)
^
mesa/src/mesa/drivers/dri/i965/brw_state_upload.c: In function
'brw_pipeline_state_finished':
mesa/src/mesa/drivers/dri/i965/brw_state_upload.c:801:13: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
if (i != pipeline) {
^
Signed-off-by:
mesa/src/mesa/drivers/dri/i965/brw_eu_compact.c: In function
'set_3src_source_index':
mesa/src/mesa/drivers/dri/i965/brw_eu_compact.c:839:22: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < ARRAY_SIZE(gen8_3src_source_index_table);
In file included from mesa/src/mesa/main/get.c:495:0:
mesa/src/mesa/main/get_hash.h:180:5: warning: missing initializer for field
'extra' of 'const struct value_desc' [-Wmissing-field-initializers]
{ GL_POINT_SIZE_ARRAY_BUFFER_BINDING_OES, LOC_CUSTOM, TYPE_INT, 0 },
^
Resolve a series of missing field initializer warnings within get_hash_params.py
This changeset addresses some likely code rot around the *extra field, where the
initialization is via C code generated indirectly from a Python script.
As a new contributor, I am continuing to focus on manageable,
In file included from mesa/src/mesa/main/get.c:495:0:
mesa/src/mesa/main/get.c:190:37: warning: missing initializer for field 'extra'
of 'const struct value_desc' [-Wmissing-field-initializers]
LOC_ARRAY, type, offsetof(struct gl_vertex_array_object, field)
In file included from mesa/src/mesa/main/get.c:495:0:
mesa/src/mesa/main/get.c:190:37: warning: missing initializer for field 'extra'
of 'const struct value_desc' [-Wmissing-field-initializers]
LOC_ARRAY, type, offsetof(struct gl_vertex_array_object, field)
In file included from mesa/src/mesa/main/get.c:495:0:
mesa/src/mesa/main/get.c:190:37: warning: missing initializer for field 'extra'
of 'const struct value_desc' [-Wmissing-field-initializers]
LOC_ARRAY, type, offsetof(struct gl_vertex_array_object, field)
Thanks! I think I would have squashed these together in one patch, it is
the same one-line fix in 4 consecutive lines after all. In any case,
this series is:
Reviewed-by: Iago Toral Quiroga
On Tue, 2015-09-08 at 20:21 +1000, Rhys Kidd wrote:
> Resolve a series of missing
mesa/src/glsl/nir/nir_search.c: In function 'match_value':
mesa/src/glsl/nir/nir_search.c:110:28: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < num_components; ++i) {
^
Signed-off-by: Rhys Kidd
mesa/src/glsl/nir/nir_search.c: In function 'match_value':
mesa/src/glsl/nir/nir_search.c:139:19: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
if (i < num_components)
^
Signed-off-by: Rhys Kidd
---
mesa/src/glsl/nir/nir_lower_tex_projector.c: In function
'nir_lower_tex_projector_block':
mesa/src/glsl/nir/nir_lower_tex_projector.c:114:38: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (int i = proj_index + 1; i < tex->num_srcs; i++) {
mesa/src/glsl/nir/nir_search.c: In function 'match_value':
mesa/src/glsl/nir/nir_search.c:84:22: warning: comparison between signed and
unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < num_components; ++i)
^
Signed-off-by: Rhys Kidd
mesa/src/glsl/nir/nir_lower_tex_projector.c: In function
'nir_lower_tex_projector_block':
mesa/src/glsl/nir/nir_lower_tex_projector.c:53:39: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (proj_index = 0; proj_index < tex->num_srcs; proj_index++)
Continued progress towards addressing all GCC sign-compare warnings across
Mesa (at least as compiled for i965 hw).
As a new contributor, I am continuing to focus on manageable, easily reviewed,
discrete improvements. This patchset resolves a number of warnings reported
by GCC when configured to
On Tue, 2015-09-08 at 20:21 +1000, Rhys Kidd wrote:
> Resolve a series of missing field initializer warnings within
> get_hash_params.py
>
> This changeset addresses some likely code rot around the *extra
> field, where the
> initialization is via C code generated indirectly from a Python
>
On 09/06/2015 09:37 AM, Chris Wilson wrote:
> glCopyTexImage behaves similarly to glReadPixels with respect to the
> pixel transfer operations. Therefore if any are set we cannot use the
> simply blit fast paths.
Do we have any test cases that hit these paths? If not, we should
probably con
On Sun, Sep 6, 2015 at 9:37 AM, Chris Wilson wrote:
> glCopyTexImage behaves similarly to glReadPixels with respect to the
> pixel transfer operations. Therefore if any are set we cannot use the
> simply blit fast paths.
>
> Signed-off-by: Chris Wilson
On Tue, Sep 08, 2015 at 12:33:05PM -0700, Anuj Phogat wrote:
> On Sun, Sep 6, 2015 at 9:37 AM, Chris Wilson wrote:
> > glCopyTexImage behaves similarly to glReadPixels with respect to the
> > pixel transfer operations. Therefore if any are set we cannot use the
> >
On 09/06/2015 03:46 PM, Kenneth Graunke wrote:
> On Sunday, September 06, 2015 10:06:38 PM Marek Olšák wrote:
>> On Sun, Sep 6, 2015 at 8:38 PM, Emil Velikov
>> wrote:
>>> On 3 September 2015 at 20:33, Ilia Mirkin wrote:
On Thu, Sep 3, 2015
On Tue, Sep 8, 2015 at 12:58 PM, Chris Wilson wrote:
> On Tue, Sep 08, 2015 at 12:33:05PM -0700, Anuj Phogat wrote:
>> On Sun, Sep 6, 2015 at 9:37 AM, Chris Wilson
>> wrote:
>> > glCopyTexImage behaves similarly to glReadPixels with respect to
I tested this series, and found some issues:
The following tests assert on g33:
piglit.shaders.glsl-fwidth
piglit.shaders.glsl-fs-sampler-numbering
piglit.shaders.glsl-lod-bias
piglit.shaders.glsl-kwin-blur-1
piglit.shaders.glsl-bug-22603
piglit.shaders.glsl-fs-texturecube
According to the ARB_viewport_array spec, GL4 limit is higher than the
GL3 limit. Also take this opportunity to fix the GL3 limit.
Signed-off-by: Ilia Mirkin
Cc: "11.0"
---
src/mesa/state_tracker/st_extensions.c | 9 +++--
1 file
Reviewed-by: Marek Olšák
Marek
On Tue, Sep 8, 2015 at 10:59 PM, Ilia Mirkin wrote:
> According to the ARB_viewport_array spec, GL4 limit is higher than the
> GL3 limit. Also take this opportunity to fix the GL3 limit.
>
> Signed-off-by: Ilia Mirkin
Reviewed-by: Jordan Justen
On 2015-08-05 01:30:22, Iago Toral Quiroga wrote:
> From: Samuel Iglesias Gonsalvez
>
> Notice that we should differentiate betweeb shader storage blocks and
> uniform blocks, since they have different limits.
>
>
On Mon, Sep 7, 2015 at 3:09 PM, Timothy Arceri wrote:
> On Mon, 2015-09-07 at 11:24 -0700, Jason Ekstrand wrote:
>> On Tue, Sep 1, 2015 at 7:44 PM, Timothy Arceri
>> wrote:
>> > This allows the correct offset to be easily calculated for indirect
>> >
Reviewed-by: Jordan Justen
On 2015-08-05 01:30:23, Iago Toral Quiroga wrote:
> From: Samuel Iglesias Gonsalvez
>
> Signed-off-by: Samuel Iglesias Gonsalvez
> ---
> src/glsl/link_uniforms.cpp | 15 ++-
> 1 file
On Tue, 2015-09-08 at 20:12 +1000, Rhys Kidd wrote:
> Continued progress towards addressing all GCC sign-compare warnings
> across
> Mesa (at least as compiled for i965 hw).
>
> As a new contributor, I am continuing to focus on manageable, easily
> reviewed,
> discrete improvements. This patchset
This pass can be used as a helper for NIR producers so they don't have to
worry about creating the temporaries themselves.
---
src/glsl/Makefile.sources | 1 +
src/glsl/nir/nir.h | 2 +
src/glsl/nir/nir_lower_outputs_to_temporaries.c | 131
---
src/glsl/nir/glsl_to_nir.cpp | 2 ++
src/mesa/drivers/dri/i965/brw_shader.cpp | 3 ---
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/glsl/nir/glsl_to_nir.cpp b/src/glsl/nir/glsl_to_nir.cpp
index 0712908..ad7d7dd 100644
--- a/src/glsl/nir/glsl_to_nir.cpp
+++
---
src/glsl/nir/nir.h | 11 +++
src/glsl/nir/nir_from_ssa.c | 7 +--
2 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/src/glsl/nir/nir.h b/src/glsl/nir/nir.h
index e73b7fb..c4db005 100644
--- a/src/glsl/nir/nir.h
+++ b/src/glsl/nir/nir.h
@@ -1608,6 +1608,17
On 09/03/2015 06:03 AM, Francisco Jerez wrote:
> IVB and VLV hang sporadically when an untyped surface read or write
> message is used to access a surface of format other than RAW, as may
> happen when there is a mismatch between the format qualifier of the
> image uniform and the format of the
When I tested this, I saw an intermittent BSW gpu hang. I haven't been
able to confirm that it is due to the host-mem-barrier test.
-Mark
Francisco Jerez writes:
> The hardware documentation relating to the UAV HW-assisted coherency
> mechanism and UAV access enable
This fixes a GPU hang on IVB, which is triggered with
piglit.spec.arb_shader_image_load_store.invalid
Tested-by: Mark Janes
Francisco Jerez writes:
> IVB and VLV hang sporadically when an untyped surface read or write
> message is used to access
Resolve a series of missing field initializer warnings within get_hash_params.py
Of the form:
In file included from mesa/src/mesa/main/get.c:495:0:
mesa/src/mesa/main/get_hash.h:180:5: warning: missing initializer for field
'extra' of 'const struct value_desc' [-Wmissing-field-initializers]
mesa/src/mesa/program/prog_to_nir.c: In function
'setup_registers_and_variables':
/mesa/src/mesa/program/prog_to_nir.c:1059:22: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < c->prog->NumTemporaries; i++) {
^
Continued progress towards addressing all GCC sign-compare warnings across
Mesa (at least as compiled for i965 hw).
As a new contributor, I am continuing to focus on manageable, easily reviewed,
discrete improvements. This patchset resolves a number of warnings reported
by GCC when configured to
mesa/src/glsl/nir/nir_lower_tex_projector.c: In function
'nir_lower_tex_projector_block':
mesa/src/glsl/nir/nir_lower_tex_projector.c:63:25: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < tex->num_srcs; i++) {
mesa/src/mesa/drivers/dri/i965/brw_eu_compact.c: In function
'set_3src_control_index':
mesa/src/mesa/drivers/dri/i965/brw_eu_compact.c:805:22: warning: comparison
between signed and unsigned integer expressions [-Wsign-compare]
for (int i = 0; i < ARRAY_SIZE(gen8_3src_control_index_table);
On 09/08/2015 04:51 PM, Jason Ekstrand wrote:
> This pass can be used as a helper for NIR producers so they don't have to
> worry about creating the temporaries themselves.
> ---
> src/glsl/Makefile.sources | 1 +
> src/glsl/nir/nir.h | 2 +
>
On Tue, Sep 8, 2015 at 5:30 PM, Ian Romanick wrote:
> On 09/08/2015 04:51 PM, Jason Ekstrand wrote:
>> This pass can be used as a helper for NIR producers so they don't have to
>> worry about creating the temporaries themselves.
>> ---
>> src/glsl/Makefile.sources
---
src/glsl/Makefile.sources| 1 +
src/glsl/nir/nir.h | 1 +
src/glsl/nir/nir_move_vec_src_uses_to_dest.c | 190 +++
3 files changed, 192 insertions(+)
create mode 100644 src/glsl/nir/nir_move_vec_src_uses_to_dest.c
diff
The idea here is not that it gives register coalescing a little bit of a
helping hand. It doesn't actually fix the coalescing problems, but it
seems to help a good bit.
Shader-db results for vec4 programs on Haswell:
total instructions in shared programs: 1801527 -> 1761720 (-2.21%)
---
src/glsl/nir/nir.c | 18 ++
src/glsl/nir/nir.h | 4
2 files changed, 22 insertions(+)
diff --git a/src/glsl/nir/nir.c b/src/glsl/nir/nir.c
index 3f4bec4..156fe94 100644
--- a/src/glsl/nir/nir.c
+++ b/src/glsl/nir/nir.c
@@ -1404,3 +1404,21 @@
Mark Janes writes:
> When I tested this, I saw an intermittent BSW gpu hang. I haven't been
> able to confirm that it is due to the host-mem-barrier test.
>
It would probably be useful to know if the hang is due to any of the
image load/store tests or if it's something
On 09/07/2015 01:58 AM, Emil Velikov wrote:
> From: Matt Turner
>
> v2: [Emil Velikov]
> Rework the error path to a common goto, close only if we own the fd.
>
> Signed-off-by: Emil Velikov
> ---
> src/egl/drivers/dri2/platform_drm.c | 27
Our old value of 16384 is the minimum value. DirectX apparently
requires 65536 at a minimum; that's also what nVidia and the Intel
Windows driver advertise. AMD advertises MAX_INT.
Ilia Mirkin noticed that "Shadow Warrior" uses UBOs larger than 16k
on Nouveau, which advertises 65536 bytes for
Signed-off-by: Ilia Mirkin
[v2: kayden-supplied code in fs_nir replacing need for logical opcode]
---
v1 -> v2:
- Fix sampleinfo comment in vec4 to reflect why it's necessary
- Remove the LOGICAL opcode variant
- Avoid calling emit_texture from fs_nir entirely, using
On 08/27/2015 08:48 PM, Ilia Mirkin wrote:
> Signed-off-by: Ilia Mirkin
> ---
> src/mesa/main/extensions.c | 1 +
> src/mesa/main/mtypes.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/src/mesa/main/extensions.c b/src/mesa/main/extensions.c
> index
On Tue, Sep 8, 2015 at 11:05 PM, Ian Romanick wrote:
> On 08/27/2015 08:48 PM, Ilia Mirkin wrote:
>> Signed-off-by: Ilia Mirkin
>> ---
>> src/mesa/main/extensions.c | 1 +
>> src/mesa/main/mtypes.h | 1 +
>> 2 files changed, 2 insertions(+)
>>
>>
On 09/08/2015 08:17 PM, Ian Romanick wrote:
> On 09/08/2015 08:10 PM, Ilia Mirkin wrote:
>> I'll give it a shot on NVIDIA and see what happens... my tests might
>> require GL 3.2 because I didn't want to deal with the various
>> differences that happen otherwise.
>
> That should be good enough.
On Tue, Sep 8, 2015 at 11:38 PM, Ian Romanick wrote:
> On 09/08/2015 08:17 PM, Ian Romanick wrote:
>> On 09/08/2015 08:10 PM, Ilia Mirkin wrote:
>>> I'll give it a shot on NVIDIA and see what happens... my tests might
>>> require GL 3.2 because I didn't want to deal with the
On 08/27/2015 08:48 PM, Ilia Mirkin wrote:
> Will be used for textureSamples()
>
> Signed-off-by: Ilia Mirkin
> ---
> src/glsl/ir.cpp| 5 +++--
> src/glsl/ir.h | 3 ++-
> src/glsl/ir_clone.cpp |
On 09/08/2015 08:10 PM, Ilia Mirkin wrote:
> On Tue, Sep 8, 2015 at 11:05 PM, Ian Romanick wrote:
>> On 08/27/2015 08:48 PM, Ilia Mirkin wrote:
>>> Signed-off-by: Ilia Mirkin
>>> ---
>>> src/mesa/main/extensions.c | 1 +
>>> src/mesa/main/mtypes.h
On Sun, Sep 6, 2015 at 10:13 AM, Marek Olšák wrote:
> From: Marek Olšák
>
> This fixes corruption in Unigine Heaven on VI
>
> Cc: 11.0
For the series:
Reviewed-by: Alex Deucher
> ---
>
This patch is
Reviewed-by: Ian Romanick
On 08/27/2015 08:48 PM, Ilia Mirkin wrote:
> Signed-off-by: Ilia Mirkin
> ---
> src/glsl/builtin_functions.cpp | 31 +++
> 1 file changed, 31 insertions(+)
>
> diff --git
On 09/08/2015 06:04 PM, Kenneth Graunke wrote:
> Our old value of 16384 is the minimum value. DirectX apparently
> requires 65536 at a minimum; that's also what nVidia and the Intel
> Windows driver advertise. AMD advertises MAX_INT.
>
> Ilia Mirkin noticed that "Shadow Warrior" uses UBOs
On Mon, Sep 7, 2015 at 4:06 AM, Emil Velikov
wrote:
> Hi Jon,
>
> On 4 September 2015 at 14:00, Jon TURNEY
> wrote:
> > When checking for LLVM shared libraries, use IMP_LIB_EXT for the
> extension for
> > shared libraries appropriate to the
On Fri, Sep 04, 2015 at 02:00:19PM +0100, Jon TURNEY wrote:
> When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension for
> shared libraries appropriate to the target, rather than hardcoding '.so'
>
> Also add some comments to explain why we have this circus of pain.
>
>
On Mon, Sep 07, 2015 at 10:06:49AM +0100, Emil Velikov wrote:
> Hi Jon,
>
> On 4 September 2015 at 14:00, Jon TURNEY wrote:
> > When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension
> > for
> > shared libraries appropriate to the target, rather
Hi,
If you repost with the changes suggested by the others,
and add the Reviewed-by tag when reposting, I'll pull these
down (and the other series too), and get them merged
along with one other patch I have sitting.
You can add my reviewed-by to both series.
Thanks for the effort =)
2015-09-08
On 2015-08-05 01:30:21, Iago Toral Quiroga wrote:
> From: Samuel Iglesias Gonsalvez
>
> Otherwise, generate a link time error as per the
> ARB_shader_storage_buffer_object spec.
>
> Signed-off-by: Samuel Iglesias Gonsalvez
> ---
>
On 2015-08-05 01:30:20, Iago Toral Quiroga wrote:
> From: Samuel Iglesias Gonsalvez
>
> Signed-off-by: Samuel Iglesias Gonsalvez
> ---
> src/glsl/lower_ubo_reference.cpp | 65
> ++--
> 1 file changed, 49
On 2015.09.03 at 01:54 +0300, Grazvydas Ignotas wrote:
> During review of the "r600g: make all scissor states use single atom" patch
> Marek Olšák noticed that scissor disable workaround should be applied on
> all scissor states and not just first one, so let's do so.
This patch causes:
Ben Widawsky writes:
> On Fri, Sep 04, 2015 at 02:58:30PM -0700, Ben Widawsky wrote:
>> On Wed, Sep 02, 2015 at 01:03:43PM +0100, Chris Wilson wrote:
>> > On Wed, Aug 26, 2015 at 10:52:58AM -0700, Ben Widawsky wrote:
>> > > Docs suggest this is no longer required starting with
On Tue, Sep 8, 2015 at 2:24 AM, Kenneth Graunke wrote:
> On Monday, September 07, 2015 10:51:37 AM Jason Ekstrand wrote:
>> On Sep 3, 2015 1:49 AM, "Kenneth Graunke" wrote:
>> >
>> > This patch also introduces a lowering pass to convert the simple GS
On Tuesday, September 08, 2015 08:50:41 PM Ian Romanick wrote:
> On 09/08/2015 06:04 PM, Kenneth Graunke wrote:
> > Our old value of 16384 is the minimum value. DirectX apparently
> > requires 65536 at a minimum; that's also what nVidia and the Intel
> > Windows driver advertise. AMD advertises
On Tue, 2015-09-08 at 15:25 -0700, Mark Janes wrote:
> I tested this series, and found some issues:
>
> The following tests assert on g33:
> piglit.shaders.glsl-fwidth
> piglit.shaders.glsl-fs-sampler-numbering
> piglit.shaders.glsl-lod-bias
> piglit.shaders.glsl-kwin-blur-1
>
These 2 patches are
Reviewed-by: Tapani Pälli
On 08/23/2015 11:50 AM, Jordan Justen wrote:
We lower gl_LocalInvocationIndex based on the extension spec formula:
gl_LocalInvocationIndex =
gl_LocalInvocationID.z * gl_WorkGroupSize.x * gl_WorkGroupSize.y +
On Tue, Sep 8, 2015 at 11:46 PM, Ilia Mirkin wrote:
> On Tue, Sep 8, 2015 at 11:38 PM, Ian Romanick wrote:
>> On 09/08/2015 08:17 PM, Ian Romanick wrote:
>>> On 09/08/2015 08:10 PM, Ilia Mirkin wrote:
I'll give it a shot on NVIDIA and see what
Francisco Jerez writes:
> Mark Janes writes:
>
>> When I tested this, I saw an intermittent BSW gpu hang. I haven't been
>> able to confirm that it is due to the host-mem-barrier test.
>>
> It would probably be useful to know if the hang is due to
On Saturday, September 05, 2015 11:10:58 AM Connor Abbott wrote:
> On Sat, Sep 5, 2015 at 2:31 AM, Kenneth Graunke wrote:
> > On Friday, September 04, 2015 11:56:29 AM Connor Abbott wrote:
> >> I'm confused as to how this can happen. The fake link is only for the
> >>
89 matches
Mail list logo