Reviewed-by: Iago Toral Quiroga
On Thu, 2016-12-01 at 16:07 -0800, Jason Ekstrand wrote:
> This has bothered me for about as long as NIR has been around. Why
> do we
> have two different unions for constants? No good reason other than
> one of
> them is a direct port from GLSL IR.
> ---
> src/
+Ken
On Thu, Dec 1, 2016 at 10:17 PM, Jason Ekstrand
wrote:
> I'm not sure how I feel about this one. It seems like it would almost be
> easier to just pick one convention or the other for NIR and adjust one of
> the drivers accordingly. I don't know that I have a huge preference which
> conve
I'm not sure how I feel about this one. It seems like it would almost be
easier to just pick one convention or the other for NIR and adjust one of
the drivers accordingly. I don't know that I have a huge preference which
convention we choose. I guess the Vulkan convention matches our hardware a
Build mesa 2863 completed
Commit c45d84ad83 by Timothy Arceri on 12/2/2016 5:44 AM:
Revert "st/mesa: get Version from gl_program rather than gl_shader_program"\n\nThis reverts commit 6bf63b011992dbbc899a28bde5692070dbcf965a.\n\nA patch that adds a reference to
On Fri, 2016-12-02 at 04:51 +0100, Dieter Nützel wrote:
> Hello Timothy,
>
> it fails, here:
>
> state_tracker/st_atom_texture.c: In function 'update_textures':
> state_tracker/st_atom_texture.c:130:49: error: 'const struct
> ' has no member named 'data'
>
Hello Timothy,
it fails, here:
state_tracker/st_atom_texture.c: In function 'update_textures':
state_tracker/st_atom_texture.c:130:49: error: 'const struct
' has no member named 'data'
prog->sh.data->Version);
Build mesa 2862 failed
Commit 6bf63b0119 by Timothy Arceri on 11/9/2016 4:01 AM:
st/mesa: get Version from gl_program rather than gl_shader_program\n\nReviewed-by: Nicolai Hähnle
Configure your notification preferences
__
On Fri, Nov 25, 2016 at 12:52 AM, Juan A. Suarez Romero wrote:
> From: Samuel Iglesias Gonsálvez
>
> We use *64*_PASSTHRU formats to upload vertex attributes of 64 bits
> to avoid conversions. From the BDW PRM, Volume 2d, page 586
> (VERTEX_ELEMENT_STATE):
>
> "When SourceElementFormat is s
If you don't mind rebasing on it, my "get rid of nir_constant_data" patch
should let you drop most of this and patch 5.
On Fri, Nov 25, 2016 at 12:52 AM, Juan A. Suarez Romero wrote:
> From: Samuel Iglesias Gonsálvez
>
> Signed-off-by: Samuel Iglesias Gonsálvez
> ---
> src/compiler/spirv/spir
On Fri, Nov 25, 2016 at 12:52 AM, Juan A. Suarez Romero wrote:
> From: Samuel Iglesias Gonsálvez
>
> SPIR-V does not have special opcodes for DF conversions. We need to
> identify
> them by checking the bit size of the operand and the result.
>
> Signed-off-by: Samuel Iglesias Gonsálvez
> ---
>
On Thu, 2016-12-01 at 12:38 +0100, Nicolai Hähnle wrote:
> Hmm, I wonder what the rules are when different shaders have
> different
> versions and are linked together?
Yeah I was wondering the same when I changed this. It seems that in
linker.cpp we get the max version from the shaders and store
The active_query count was incorrect for query types that don't require
a begin_query. Removed the unnecessary assert.
---
src/gallium/drivers/swr/swr_query.cpp | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/src/gallium/drivers/swr/swr_query.cpp
b/src/gallium/d
https://bugs.freedesktop.org/show_bug.cgi?id=97524
--- Comment #17 from Timothy Arceri ---
Created attachment 128306
--> https://bugs.freedesktop.org/attachment.cgi?id=128306&action=edit
Validate sampler types across the whole program
It's untested but this patch should do the trick.
Note it
On Wed, Nov 30, 2016 at 8:12 PM, Jordan Justen
wrote:
> If try_blorp_blit() previously returned that a blit was too large,
> shrink_surface_params() will be used to update the surface parameters
> for the smaller blit so the blit operation can proceed.
>
> v2:
> * Use double instead of float. (J
This has bothered me for about as long as NIR has been around. Why do we
have two different unions for constants? No good reason other than one of
them is a direct port from GLSL IR.
---
src/compiler/glsl/glsl_to_nir.cpp | 35 +---
src/compiler/nir/nir.c | 32 +++
On Thu, Dec 1, 2016 at 12:46 AM, Iago Toral wrote:
> On Tue, 2016-11-29 at 22:51 -0800, Jason Ekstrand wrote:
> > This has bothered me for about as long as NIR has been around. Why
> > do we
> > have two different unions for constants? No good reason other than
> > one of
> > them is a direct p
On Sun, Nov 27, 2016 at 1:26 AM, Kenneth Graunke wrote:
> On Tuesday, November 22, 2016 11:59:48 AM PST Matt Turner wrote:
>> A function is necessary to handle immediate types.
>> ---
>> src/mesa/drivers/dri/i965/brw_disasm.c | 35
>> src/mesa/drivers/dri/i965/brw_eu_emit.c
On 16-12-01 14:41:20, Kenneth Graunke wrote:
On Thursday, December 1, 2016 2:09:55 PM PST Ben Widawsky wrote:
From: Ben Widawsky
Previously our aux buffers (MCS, and HiZ) never had an offset because
they were in their own buffer object. When using the CCS lossless
compression feature, it's des
On Thursday, December 1, 2016 2:09:55 PM PST Ben Widawsky wrote:
> From: Ben Widawsky
>
> Previously our aux buffers (MCS, and HiZ) never had an offset because
> they were in their own buffer object. When using the CCS lossless
> compression feature, it's desirable to store the data at an offset
On Wed, 2016-11-30 at 20:23 +, Emil Velikov wrote:
> Hi all,
>
> With holidays not far off, it might be a nice idea to consider the
> branchpoint/release schedule for the next release.
>
> I will be having limited internet access during 20 Dec - 7 Jan, thus
> the I'm leaning towards following
From: Ben Widawsky
This doesn't actually enable Y-tiling, it simply parses it and moves on.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_image.h | 1 +
src/mesa/drivers/dri/i965/intel_screen.c | 36 +---
2 files changed, 29 insertions(+), 8 dele
From: Ben Widawsky
FINISHME: Use the kernel's final choice for the fb modifier
bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $)
~/scripts/measure_bandwidth.sh ./kmscube none
Read bandwidth: 603.91 MiB/s
Write bandwidth: 615.28 MiB/s
bwidawsk@norris2:~/intel-gfx/kmscube (modifiers $)
~/script
From: Ben Widawsky
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_screen.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/intel_screen.c
b/src/mesa/drivers/dri/i965/intel_screen.c
index 91eb7ec..f40761a 10064
From: Ben Widawsky
Signed-off-by: Ben Widawsky
---
src/gbm/backends/dri/gbm_dri.c | 26 +-
src/gbm/gbm-symbols-check | 1 +
src/gbm/main/gbm.c | 15 ++-
src/gbm/main/gbm.h | 3 +++
4 files changed, 43 insertions(+), 2 deletions(
From: Ben Widawsky
There is nothing particularly useful to do currently if the update
fails, but there is no point carrying on either. As a result, this has a
behavior change.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/brw_context.c | 14 --
src/mesa/drivers/dr
From: Ben Widawsky
commit 6a0d036483caf87d43ebe2edd1905873446c9589
Author: Ben Widawsky
Date: Thu Apr 21 20:14:58 2016 -0700
i965: Always use Y-tiled buffers on SKL+
Aside from the benchmark gains that were initially posted, I was able to
collect memory bandwidth data running kmscube (19
From: Ben Widawsky
On Gen9 hardware, the display engine is able to scanout a compressed
framebuffer by providing an offset to auxiliary compression information.
Unfortunately, the hardware is incapable of doing the same thing for the
fast clear color.
To mitigate this, the hardware introduced a
From: Ben Widawsky
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_screen.c | 37
1 file changed, 33 insertions(+), 4 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/intel_screen.c
b/src/mesa/drivers/dri/i965/intel_screen.c
index 0f19a6e..9
From: Ben Widawsky
Since the code doesn't support modifiers yet, this patch should do
nothing other than prepare for more patches.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_screen.c | 73 ++--
1 file changed, 60 insertions(+), 13 deletions(-)
From: Ben Widawsky
Cc: Ville Syrjälä
Cc: Jason Ekstrand
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/intel_screen.c
b/src/mesa/drivers/dri/i965/intel_screen.c
index f4076
From: Ben Widawsky
Upper layers of the code will have the need to specify full or partial
resolves (more on this in the next patch). This code simply adds the new
enums and plumbs it in as minimally as necessary.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/brw_blorp.c | 3
From: Ben Widawsky
Cc: Topi Pohjolainen
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/intel_mipmap_tree.c
b/src/mesa/drivers/dri/i965/intel_mipmap_tree.c
From: Ben Widawsky
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/brw_blorp.c | 3 ++-
src/mesa/drivers/dri/i965/brw_blorp.h | 3 ++-
src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 4 ++--
3 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/src/mesa/driver
From: Ben Widawsky
In the foreseeable future it doesn't seem to make sense to have multiple
resolve flags. What does make sense is to have the caller give an
indication to the lower layers what it things should be done for
resolve. The enum change distinguishes this binary selection.
Signed-off-
From: Ben Widawsky
Signed-off-by: Ben Widawsky
---
src/gbm/main/gbm.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/gbm/main/gbm.h b/src/gbm/main/gbm.h
index 59daaa1..efb329e 100644
--- a/src/gbm/main/gbm.h
+++ b/src/gbm/main/gbm.h
@@ -294,10 +294,10 @@ gbm_bo_map(
From: Ben Widawsky
Allows us to continue utilizing common miptree creation using __DRIimage
without creating a new DRIimage (for the intel_process_dri2_buffer()
case).
This is a bit ugly, but I think it's the best one can do.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/brw_conte
From: Ben Widawsky
This will be used so we can query information per plane.
Signed-off-by: Ben Widawsky
---
src/gbm/backends/dri/gbm_dri.c | 7 +++
src/gbm/main/gbm.c | 2 +-
src/gbm/main/gbmint.h | 1 +
3 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/src
From: Ben Widawsky
This provides a common function or creating miptrees when there is an
existing DRIimage to use. That provides an easy way to add CCS
allocation.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_fbo.c | 17 -
src/mesa/drivers/dri/i965/in
From: Ben Widawsky
This patch series ultimately adds support within the i965 driver for
Renderbuffer Decompression with GBM. In short, this feature reduces memory
bandwidth by allowing the GPU to work with losslessly compressed data and having
that compression scheme understood by the display eng
From: Ben Widawsky
Modifiers will be obtains or guessed by the client and passed in during
image creation/import.
This requires bumping the DRIimage version.
Signed-off-by: Ben Widawsky
---
include/GL/internal/dri_interface.h | 28 +++-
src/gallium/state_trackers/
From: Ben Widawsky
The idea behind modifiers like this is that the user of GBM will have
some mechanism to query what properties the hardware supports for its BO
or surface. This information is directly passed in (and stored) so that
the DRI implementation can create an image with the appropriate
From: Ben Widawsky
v2: Use stored modifiers from create instead of queryImage
Discussion with Kristian yielded that there is no need for per plane
modifiers.
Signed-off-by: Ben Widawsky
---
src/gbm/backends/dri/gbm_dri.c | 32
src/gbm/gbm-symbols-che
From: Ben Widawsky
Previously our aux buffers (MCS, and HiZ) never had an offset because
they were in their own buffer object. When using the CCS lossless
compression feature, it's desirable to store the data at an offset from
the main framebuffer, ie. share a buffer object. This patch just makes
From: Ben Widawsky
Other things are out of order, but I need to add a getter so I'm just
fixing those.
This helps people adding to GBM know where the right place to put things
is.
Signed-off-by: Ben Widawsky
---
src/gbm/main/gbm.c | 22 +++---
1 file changed, 11 insertions(+),
From: Ben Widawsky
This code will disable actually creating these buffers for the scanout,
but it puts the allocation in place.
Primarily this patch is split out for review, it can be squashed in
later if preferred.
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_mipmap_tree.c
From: Ben Widawsky
Unlike stride, there was no previous offset getter, so it can be right
on the first try.
Signed-off-by: Ben Widawsky
---
src/gbm/backends/dri/gbm_dri.c | 27 +++
src/gbm/gbm-symbols-check | 1 +
src/gbm/main/gbm.c | 15 ++
From: Ben Widawsky
This will be used by clients that need to know the number of planes
allocated for them on behalf of the GL or other API. The best current
example of this is when an extra "plane" is allocated to store
compression data for the primary plane.
Cc: Daniel Stone
Signed-off-by: Ben
From: Ben Widawsky
I intend to need to get to the devinfo structure, and storing the screen
is an easy way to do that.
It seems to be the consensus that you cannot share an image between
multiple screens.
Scape-goat: Rob Clark
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_i
This fixes a bug in code motion that occurred when the best block is the
same as the schedule early block. In this case, because we're checking
(lca != def->parent_instr->block) at the top of the loop, we never get to
the check for loop depth so we wouldn't move it out of the loop. This
commit re
On Wed, Nov 30, 2016 at 9:23 PM, Emil Velikov wrote:
> Hi all,
>
> With holidays not far off, it might be a nice idea to consider the
> branchpoint/release schedule for the next release.
>
> I will be having limited internet access during 20 Dec - 7 Jan, thus
> the I'm leaning towards following:
>
Ilia, it is different from the NV variant -- NV unfortunately threw a bunch
of other stuff in (extra subpixel bits in conservative mode).
Series is:
Reviewed-by: Chris Forbes
On Fri, Dec 2, 2016 at 8:21 AM, Ilia Mirkin wrote:
> Ah, I see. The difference is that it exists, unlike the ARB one :
On Wed, Nov 30, 2016 at 05:55:32PM -0800, Jason Ekstrand wrote:
> On Wed, Nov 30, 2016 at 10:20 AM, Nanley Chery
> wrote:
>
> > On Tue, Nov 29, 2016 at 05:41:58PM -0800, Jason Ekstrand wrote:
> > > In an attempt to fix 3DSTATE_DEPTH_BUFFER for stencil-only cases, I
> > > accidentally kept setting
Ah, I see. The difference is that it exists, unlike the ARB one :) I was
confusing with the NV variant.
On Dec 1, 2016 2:10 PM, "Ilia Mirkin" wrote:
Is this different from the arb variant?
On Dec 1, 2016 10:56 AM, "Lionel Landwerlin"
wrote:
> Signed-off-by: Lionel Landwerlin
> ---
> src/com
Is this different from the arb variant?
On Dec 1, 2016 10:56 AM, "Lionel Landwerlin"
wrote:
> Signed-off-by: Lionel Landwerlin
> ---
> src/compiler/glsl/ast.h | 5
> src/compiler/glsl/ast_to_hir.cpp | 5
> src/compiler/glsl/ast_type.cpp | 16 +
When I originally implemented the ARB_copy_image extension, the fast-path
was written in meta using texture views. This path only worked if both
images were uncompressed color images. All of the other cases fell back to
the blitter or, in the worst case, mapping and memcpy on the CPU. Now that
w
Cc: "13.0"
---
src/mesa/drivers/dri/i965/intel_blit.c | 151 ++---
1 file changed, 84 insertions(+), 67 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/intel_blit.c
b/src/mesa/drivers/dri/i965/intel_blit.c
index 4944b8c..15e45d4 100644
--- a/src/mesa/drivers/dri/
By using emit_miptree_blit which does chunking, this fixes the blitter path
for the case where the image is too tall to blit normally. We also pull it
into intel_blit as intel_miptree_copy. This matches the naming of the
blorp blit and copy functions brw_blorp_blit and brw_blorp_copy.
Cc: "13.0"
Hi Rob, just checking on the status on the patch set. Do you plan to
send a revised series or commit them as-is? I ask because my i965
patches depend on your patches 1-4, and I'm trying to decide to when to
resend them.
On Fri 18 Nov 2016, Rob Clark wrote:
> This patchset implements support for EG
Reviewed-by: Marek Olšák
Marek
On Thu, Dec 1, 2016 at 6:14 PM, Tim Rowley wrote:
> ---
> src/gallium/auxiliary/tgsi/tgsi_scan.c | 3 +++
> src/gallium/auxiliary/tgsi/tgsi_scan.h | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/src/gallium/auxiliary/tgsi/tgsi_scan.c
> b/src/gallium/a
---
src/gallium/auxiliary/tgsi/tgsi_scan.c | 3 +++
src/gallium/auxiliary/tgsi/tgsi_scan.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/src/gallium/auxiliary/tgsi/tgsi_scan.c
b/src/gallium/auxiliary/tgsi/tgsi_scan.c
index 84d6456..77fe6b3 100644
--- a/src/gallium/auxiliary/tgsi/tgsi_scan
On 11/30/2016 12:19 PM, Matt Turner wrote:
> On 11/28, Ian Romanick wrote:
>> From: Ian Romanick
[snip]
>> + if (parser->extension_list) {
>> + /* If MESA_shader_integer_functions is supported, then the
>> building
>> + * blocks required for the 64x64 => 64 multiply exist. Add
>> d
On 11/30/2016 12:46 PM, Matt Turner wrote:
> On 11/28, Ian Romanick wrote:
>> From: Ian Romanick
>>
>> These functions are directly available in shaders. A #define is added
>> to detect the presence. This allows these functions to be tested using
>> piglit regardless of whether the driver uses t
Forgot to mentioned that this is based on top of Plamena's work (in case
you want to test) :
https://patchwork.freedesktop.org/series/15512/
On 01/12/16 15:56, Lionel Landwerlin wrote:
Hi,
Here are a couple of patches to add support for the
INTEL_conservative_rasterization extension.
This is
Signed-off-by: Lionel Landwerlin
---
docs/relnotes/13.1.0.html| 1 +
src/mesa/drivers/dri/i965/brw_compiler.h | 1 +
src/mesa/drivers/dri/i965/brw_defines.h | 1 +
src/mesa/drivers/dri/i965/brw_fs.cpp | 1 +
src/mesa/drivers/dri/i965/gen8_ps_state.c| 1
Hi,
Here are a couple of patches to add support for the
INTEL_conservative_rasterization extension.
This is available on Gen9+ platforms.
You can find associated piglit tests here :
https://patchwork.freedesktop.org/series/16230/
Cheers,
Lionel Landwerlin (2):
mesa: add support for GL_INT
Signed-off-by: Lionel Landwerlin
---
src/compiler/glsl/ast.h | 5
src/compiler/glsl/ast_to_hir.cpp | 5
src/compiler/glsl/ast_type.cpp | 16 +++-
src/compiler/glsl/glsl_parser.yy | 34 ++
src/compiler/glsl/glsl
Hi Christian,
Hats off for the tremendous work - both to you and fellow etnaviv hackers !
On 30 November 2016 at 13:44, Christian Gmeiner
wrote:
> As the original patchstack is now about 300 patches, I have choosen to
> squash the patches together into three different parts.
>
> - etnaviv galli
On 30 November 2016 at 13:44, Christian Gmeiner
wrote:
> The imx (stub) driver is needed to get hardware acceleration from
> etnaviv on a platform using imx-drm kms driver. This adds support
> for wayland and native kms egl apps.
>
> Signed-off-by: Christian Gmeiner
> ---
> configure.ac
On 1 December 2016 at 12:00, Nicolai Hähnle wrote:
> Congratulations on a huge amount of work! Obviously I can't say much about
> the driver itself. Some things that I noticed for the renderonly library.
>
> On 30.11.2016 14:44, Christian Gmeiner wrote:
>>
>> This a very lightweight library to add
Congratulations on a huge amount of work! Obviously I can't say much
about the driver itself. Some things that I noticed for the renderonly
library.
On 30.11.2016 14:44, Christian Gmeiner wrote:
This a very lightweight library to add basic support for
renderonly GPUs. It does all the magic reg
Hmm, I wonder what the rules are when different shaders have different
versions and are linked together? Then again, the use of the
glsl_version in st_sampler_view.c pretty much admits that it's already a
hack, so I think this is fine.
Patches 49 & 50:
Reviewed-by: Nicolai Hähnle
On 20.11.2
Patches 44-48:
Reviewed-by: Nicolai Hähnle
On 20.11.2016 14:29, Timothy Arceri wrote:
We no longer need anything from gl_linked_shader.
---
src/mesa/state_tracker/st_atom_constbuf.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/mesa/state_t
On 12/01/2016 12:59 PM, Ilia Mirkin wrote:
On Thu, Dec 1, 2016 at 5:50 AM, Tapani Pälli wrote:
On 12/01/2016 12:19 PM, Tapani Pälli wrote:
On 12/01/2016 12:04 AM, Ilia Mirkin wrote:
We were previously also verifying that no backing buffers were available
when an array wasn't enabled. T
On Thu, Dec 1, 2016 at 5:50 AM, Tapani Pälli wrote:
>
>
> On 12/01/2016 12:19 PM, Tapani Pälli wrote:
>>
>>
>> On 12/01/2016 12:04 AM, Ilia Mirkin wrote:
>>>
>>> We were previously also verifying that no backing buffers were available
>>> when an array wasn't enabled. This is has no basis in the s
On 12/01/2016 12:19 PM, Tapani Pälli wrote:
On 12/01/2016 12:04 AM, Ilia Mirkin wrote:
We were previously also verifying that no backing buffers were available
when an array wasn't enabled. This is has no basis in the spec, and it
causes GLupeN64 to fail as a result.
I'm a bit puzzled about
On 12/01/2016 12:04 AM, Ilia Mirkin wrote:
We were previously also verifying that no backing buffers were available
when an array wasn't enabled. This is has no basis in the spec, and it
causes GLupeN64 to fail as a result.
I'm a bit puzzled about the API usage here, is the app attempting to
2016-11-30 21:23 GMT+01:00 Emil Velikov :
> Hi all,
>
> With holidays not far off, it might be a nice idea to consider the
> branchpoint/release schedule for the next release.
>
> I will be having limited internet access during 20 Dec - 7 Jan, thus
> the I'm leaning towards following:
> Jan 13 201
On 01/12/16 04:02, Chris Forbes wrote:
A couple of notes on existing weirdness here:
- Naming of GEN9_PSX_SHADER_NORMAL_COVERAGE_MASK_SHIFT is bizarre (not
your fault)
- Is BRW_PSICMS_INNER really the right thing for the normal mode? Why
not BRW_PSICMS_NORMAL? Perhaps whoever added this stuff c
On 30.11.2016 21:23, Emil Velikov wrote:
Hi all,
With holidays not far off, it might be a nice idea to consider the
branchpoint/release schedule for the next release.
+1 on the 17.0 question.
I will be having limited internet access during 20 Dec - 7 Jan, thus
the I'm leaning towards follow
On 30.11.2016 22:58, Timothy Arceri wrote:
34953f8907fdd added this bitmask but it wasn't being reset when
a program was relinked. If a stage was removed from the new
program then it could case a crash as we expect the linked shader
for that stage to not be null.
Fixes crashes in:
ESEXT-CTS.tess
On Tue, 2016-11-29 at 22:51 -0800, Jason Ekstrand wrote:
> This has bothered me for about as long as NIR has been around. Why
> do we
> have two different unions for constants? No good reason other than
> one of
> them is a direct port from GLSL IR.
> ---
> src/compiler/glsl/glsl_to_nir.cpp | 3
81 matches
Mail list logo
