On 02/10/2017 03:38 AM, Timothy Arceri wrote:
The option to disable shader cache was removed from the build options
when we imported a sha1 implementation into Mesa.
Have the issues mentioned in 9f8dc3bf03ec825bae7041858dda6ca2e9a34363
been fixed?
Cc: Emil Velikov
---
src/util/disk_cach
On SM35 there does not appear to be a way to emit a ATOM.EXCH with a
null destination. This should be functionally equivalent to a plain
store however, so just do that.
Fixes GL45-CTS.compute_shader.atomic-case2 on SM35.
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/codegen/nv50_ir
On Thu, Feb 9, 2017 at 4:16 PM, Jan Ziak <0xe2.0x9a.0...@gmail.com> wrote:
> Hello
>
> IMPORTANT NOTE: Using the uint32_t data type, quad_hash*quad_hash will
> overflow as soon as the hash table has more than 2**16=65536=64K
> elements. To enable more than 64K elements in hash table, the data
> typ
On Feb 9, 2017 8:25 PM, "Dave Airlie" wrote:
From: Dave Airlie
If a buffer is just full of flushes we flush things on command
buffer submission, so don't bother submitting these.
This will reduce some CPU overhead on dota2, which submits a fair
few command streams that don't end up drawing any
Series tested with vmware svga driver. Changes looks good.
Tested-by: Charmaine Lee
From: mesa-dev on behalf of Marek
Olšák
Sent: Wednesday, February 8, 2017 4:11:01 PM
To: mesa-dev@lists.freedesktop.org
Subject: [Mesa-dev] [PATCH 00/11] Gallium common
From: Dave Airlie
If a buffer is just full of flushes we flush things on command
buffer submission, so don't bother submitting these.
This will reduce some CPU overhead on dota2, which submits a fair
few command streams that don't end up drawing anything.
Signed-off-by: Dave Airlie
---
src/am
From: Dave Airlie
This just fixes this without repeating the code.
Reported-by: Li Qiang
Signed-off-by: Dave Airlie
---
src/gallium/auxiliary/tgsi/tgsi_sanity.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/gallium/auxiliary/tgsi/tgsi_sanity.c
b/src/gallium/a
Francisco Jerez writes:
> ---
> This replaces "[PATCH v2 09/20] i965/fs: indirect addressing with
> doubles is not supported in IVB/BYT".
>
Note that some of the fp64 indirect addressing test-cases still fail on
IVB even with this patch applied, but the reason doesn't seem to have
anything to do
On 10 February 2017 at 00:35, wrote:
> From: Marc-André Lureau
>
> Since vtest is currently only handling a context at a time, calling
> disconnect in virgl_vtest_winsys_destroy() allows to pass tests such as
> piglit egl-create-context-invalid-flag-gles.
>
> Signed-off-by: Marc-André Lureau
>
---
This replaces "[PATCH v2 09/20] i965/fs: indirect addressing with
doubles is not supported in IVB/BYT".
src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 27 --
1 file changed, 25 insertions(+), 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs_generator.cpp
---
src/amd/vulkan/radv_device.c | 22 +++---
src/intel/vulkan/anv_device.c | 20 ++--
src/util/disk_cache.h | 17 +
3 files changed, 22 insertions(+), 37 deletions(-)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
On Thu, Feb 09, 2017 at 11:38:31AM -0800, Jason Ekstrand wrote:
> On Thu, Feb 9, 2017 at 10:33 AM, Nanley Chery wrote:
>
> > On Wed, Feb 08, 2017 at 06:27:52PM -0800, Jason Ekstrand wrote:
> > > On Wed, Feb 8, 2017 at 5:34 PM, Nanley Chery
> > wrote:
> > >
> > > > On Thu, Feb 02, 2017 at 01:26:0
On Wed, 2017-02-08 at 21:35 +0100, Thomas Helland wrote:
> I was cleaning up my local git repo, and came across this series.
> Last time it was discussed was all the way back in April 2015.
> Things looked pretty good back then, but we where seeing a smaller
> regression in CPU-bound scenarios as E
From: Marc-André Lureau
The instruction has an associated label when Instruction.Label == 1,
as can be seen in ureg_emit_label() or tgsi_build_full_instruction().
This fixes dump generating extra :0 labels on conditionals, and virgl
parsing more than the expected tokens and eventually reaching "
On Wed, 2017-02-08 at 15:54 -0800, Jason Ekstrand wrote:
> On Wed, Feb 8, 2017 at 2:20 PM, Elie Tournier m> wrote:
> > Signed-off-by: Elie Tournier
> > ---
> > src/compiler/nir/nir_opt_loop_unroll.c | 10 +-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/src/com
On Wed, 2017-02-08 at 15:59 -0800, Jason Ekstrand wrote:
> On Wed, Feb 8, 2017 at 3:01 PM, Marek Olšák wrote:
> > I think this is good stuff. I'd gladly take it just for the shader-
> > db
> > improvement.
> >
>
> Agreed. If it really did hurt minecraft before, we should try that
> again just t
From: Marc-André Lureau
Since vtest is currently only handling a context at a time, calling
disconnect in virgl_vtest_winsys_destroy() allows to pass tests such as
piglit egl-create-context-invalid-flag-gles.
Signed-off-by: Marc-André Lureau
---
src/gallium/winsys/virgl/vtest/virgl_vtest_socke
From: Marc-André Lureau
Unused since commit 2897cb3dba9287011f9c43cd2f214100952370c0.
Signed-off-by: Marc-André Lureau
---
src/gallium/auxiliary/tgsi/tgsi_ureg.c | 31 ---
src/gallium/auxiliary/tgsi/tgsi_ureg.h | 7 ---
2 files changed, 38 deletions(-)
diff --
https://bugs.freedesktop.org/show_bug.cgi?id=99692
--- Comment #3 from Nicholas Disiere ---
I can confirm that this visual corruption is present on my R9 290 when radeon
is blacklisted on the current Arch kernel. It affects the desktop with and
without the compositor, and causes vulkan games to c
On Fri, Feb 10, 2017 at 12:44:02AM +, Emil Velikov wrote:
> On 24 January 2017 at 00:55, Nanley Chery wrote:
> > Cc: "13.0 17.0"
> Nanley please take a look at the nominations page [1] and especially
> at the note in the end ;-)
> That said, I've picked this for 13.0 and will do 17.0 in a few
The option to disable shader cache was removed from the build options
when we imported a sha1 implementation into Mesa.
Cc: Emil Velikov
---
src/util/disk_cache.h | 50 --
1 file changed, 50 deletions(-)
diff --git a/src/util/disk_cache.h b/src/ut
On Wed, Feb 01, 2017 at 05:43:55PM -0800, Jason Ekstrand wrote:
> This seemed to help Dota 2 by a percent or two.
I wasn't able to reproduce this on SKL, could you qualify this with "on
BDW"?
> ---
> src/intel/vulkan/genX_pipeline.c | 133
> +--
> 1 file chan
The former logic just plain didn't work at all. We need to write the
subsequent dword to the next buffer location.
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/nvc0/mme/com9097.mme | 22 -
src/gallium/drivers/nouveau/nvc0/mme/com9097.mme.h | 28 ++-
Reviewed-by: Tobias Droste
Am Donnerstag, 9. Februar 2017, 20:54:26 CET schrieb Emil Velikov:
> From: Tobias Droste
>
> Set FOUND_LLVM only when LLVM is present (checking for exact version/etc
> is deferred) and use enable-gallium-llvm to indicate the global LLVM
> status.
>
> Renaming the lat
Reviewed-by: Tobias Droste for v2, too
Am Donnerstag, 9. Februar 2017, 20:57:45 CET schrieb Emil Velikov:
> From: Emil Velikov
>
> Earlier refactoring commits changed from one, dare I say it, broken
> behaviour to another. Namely:
>
> Before, as you explicitly --enable-gallium-llvm your select
Am Donnerstag, 9. Februar 2017, 20:53:06 CET schrieb Emil Velikov:
> From: Emil Velikov
>
> ... to where it's applicable.
>
> Since we effectively made --enable-gallium-llvm mean --enable-llvm with
> earlier commits, we need to move the requirement to guard the compnents
> added for the LLVM dra
From: Dave Airlie
Just noticed we do a fair bit of unneeded searching here.
Since we know that the buffers in a CS are unique already,
the first time we get any buffers, we can just memcpy those into
place, and when we are searching for subsequent CSes, we only
have to search up until where the
On 09/02/17 10:50 PM, Emil Velikov wrote:
> On 9 February 2017 at 08:07, Michel Dänzer wrote:
>> From: Michel Dänzer
>>
>> Drop all -m*, -W*, -O*, -g* and -f* flags, with the exception of
>> -fno-rtti, which must be used if it's part of the llvm-config --cxxflags
>> output. We don't want LLVM to
https://bugs.freedesktop.org/show_bug.cgi?id=99747
APoliTech changed:
What|Removed |Added
Component|Other |Drivers/Gallium/radeonsi
QA Contact|
https://bugs.freedesktop.org/show_bug.cgi?id=99747
Bug ID: 99747
Summary: Problems with mesa 13.0.x and ubuntu 17.04
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: other
Status: NEW
Severity: cri
On Thu, Feb 9, 2017 at 8:18 PM, Marek Olšák wrote:
> On Thu, Feb 9, 2017 at 6:23 PM, Ian Romanick wrote:
>> On 02/09/2017 03:03 PM, Marek Olšák wrote:
>>> On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick wrote:
On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
> On 07.02.2017 23:54, Matt Turner
On Thu, Feb 9, 2017 at 4:45 PM, Emil Velikov
wrote:
> On 10 February 2017 at 00:44, Emil Velikov
> wrote:
> > On 24 January 2017 at 00:55, Nanley Chery wrote:
> >> Cc: "13.0 17.0"
> > Nanley please take a look at the nominations page [1] and especially
> > at the note in the end ;-)
> > That s
On 10 February 2017 at 00:44, Emil Velikov wrote:
> On 24 January 2017 at 00:55, Nanley Chery wrote:
>> Cc: "13.0 17.0"
> Nanley please take a look at the nominations page [1] and especially
> at the note in the end ;-)
> That said, I've picked this for 13.0 and will do 17.0 in a few minutes.
>
On 24 January 2017 at 00:55, Nanley Chery wrote:
> Cc: "13.0 17.0"
Nanley please take a look at the nominations page [1] and especially
at the note in the end ;-)
That said, I've picked this for 13.0 and will do 17.0 in a few minutes.
Thanks
Emil
[1] https://www.mesa3d.org/submittingpatches.html
Samuel Iglesias Gonsálvez writes:
> From: "Juan A. Suarez Romero"
>
> Take in account the offset value when getting the var from register.
>
> This is required when dealing with an operation that writes half of the
> register (like one d2x in IVB/BYT, which uses exec_size == 4).
>
> Note that fo
Ian Romanick writes:
> [ Unknown signature status ]
> On 02/09/2017 05:14 PM, Eric Anholt wrote:
>> Ian Romanick writes:
>>
>>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
On 07.02.2017 23:54, Matt Turner wrote:
> On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
>> On Tue, Fe
d_type is not supported on all systems.
Tested-by: Vinson Lee
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97967
---
src/util/disk_cache.c | 33 -
1 file changed, 24 insertions(+), 9 deletions(-)
diff --git a/src/util/disk_cache.c b/src/util/disk_cache.
It's trivial to swizzle clear colors on the CPU, easily deals with the
hardware restrictions for render target swizzles, and makes swizzled
clears work on all hardware as opposed to just HSW+.
---
src/intel/blorp/blorp_clear.c | 48 +++
1 file changed, 30 in
BLORP is now smart enough to handle any swizzle (even those that contain
ZERO or ONE) in a reasonable manner. Just let BLORP handle it. This
fixes the following Vulkan CTS tests on Haswell:
- dEQP-VK.api.image_clearing.clear_color_image.1d_b4g4r4a4_unorm_pack16
- dEQP-VK.api.image_clearing.cle
https://bugs.freedesktop.org/show_bug.cgi?id=97967
--- Comment #19 from Vinson Lee ---
Applied attachment 129406. make check passes.
Mesa 17.1.0-devel: src/compiler/test-suite.log
# TOTA
From: Nicolai Hähnle
Otherwise we would fail with "implicit declaration of function" geteuid
and getenv respectively.
To trigger (re)move the libdrm.pc file and use the following:
$ ./autogen.sh --disable-egl --disable-gbm --disable-dri \
--with-dri-drivers=swrast --with-gallium-drivers=sw
https://bugs.freedesktop.org/show_bug.cgi?id=99701
--- Comment #3 from Vinson Lee ---
Applied attachment 129378. The build still fails.
$ ./autogen.sh --disable-egl --disable-gbm --disable-dri
--with-dri-drivers=swrast --with-gallium-drivers=swrast
$ make
[...]
CC libloader_la-loader.lo
lo
Hello
IMPORTANT NOTE: Using the uint32_t data type, quad_hash*quad_hash will
overflow as soon as the hash table has more than 2**16=65536=64K
elements. To enable more than 64K elements in hash table, the data
types need to be changed to uint64_t - unfortunately uint64_t
arithmetic operations will
From: Emil Velikov
Earlier refactoring commits changed from one, dare I say it, broken
behaviour to another. Namely:
Before, as you explicitly --enable-gallium-llvm your selection was
ignored when llvm-config was not present/detected.
Today, the "auto" heuristics enables gallium llvm regardless
From: Tobias Droste
Set FOUND_LLVM only when LLVM is present (checking for exact version/etc
is deferred) and use enable-gallium-llvm to indicate the global LLVM
status.
Renaming the latter is not appropriate for stable patches, so we'll
address it with a later commit.
Loosely based on work by
From: Emil Velikov
... to where it's applicable.
Since we effectively made --enable-gallium-llvm mean --enable-llvm with
earlier commits, we need to move the requirement to guard the compnents
added for the LLVM draw.
Otherwise we'll error (as below) when building RADV w/o gallium drivers.
con
Nice catch.
Reviewed-by: Samuel Pitoiset
On 02/09/2017 09:37 PM, Ilia Mirkin wrote:
We just increased the max UBO, so we should also increase the clamp that
we do for robustness. Similarly, as we're including the fileIndex in the
new indirect value, we should reset fileIndex to 0 so that it is
We just increased the max UBO, so we should also increase the clamp that
we do for robustness. Similarly, as we're including the fileIndex in the
new indirect value, we should reset fileIndex to 0 so that it is not
added in a second time.
Signed-off-by: Ilia Mirkin
Cc: mesa-sta...@lists.freedeskt
Samuel Iglesias Gonsálvez writes:
> It is tested empirically that IVB/BYT don't support indirect addressing
> with doubles but it is not documented in the PRM.
>
> This patch applies the same solution than for Cherryview/Broxton and
> takes into account that we cannot double the stride, since the
On Thu, Feb 9, 2017 at 10:33 AM, Nanley Chery wrote:
> On Wed, Feb 08, 2017 at 06:27:52PM -0800, Jason Ekstrand wrote:
> > On Wed, Feb 8, 2017 at 5:34 PM, Nanley Chery
> wrote:
> >
> > > On Thu, Feb 02, 2017 at 01:26:05PM -0800, Jason Ekstrand wrote:
> > > > In order to get good performance numb
On Thu, Feb 9, 2017 at 6:23 PM, Ian Romanick wrote:
> On 02/09/2017 03:03 PM, Marek Olšák wrote:
>> On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick wrote:
>>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
On 07.02.2017 23:54, Matt Turner wrote:
> On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák
On Wed, Feb 01, 2017 at 05:43:54PM -0800, Jason Ekstrand wrote:
> ---
> src/intel/vulkan/genX_pipeline.c | 34 ++
> 1 file changed, 18 insertions(+), 16 deletions(-)
This patch is
Reviewed-by: Nanley Chery
>
> diff --git a/src/intel/vulkan/genX_pipeline.c
> b/s
On Wed, Feb 08, 2017 at 09:38:52PM -0800, Jason Ekstrand wrote:
> On Wed, Feb 8, 2017 at 8:11 PM, Jason Ekstrand wrote:
>
> > On Wed, Feb 8, 2017 at 6:27 PM, Jason Ekstrand
> > wrote:
> >
> >> On Wed, Feb 8, 2017 at 5:34 PM, Nanley Chery
> >> wrote:
> >>
> >>> On Thu, Feb 02, 2017 at 01:26:05PM
On Wed, Feb 08, 2017 at 06:27:52PM -0800, Jason Ekstrand wrote:
> On Wed, Feb 8, 2017 at 5:34 PM, Nanley Chery wrote:
>
> > On Thu, Feb 02, 2017 at 01:26:05PM -0800, Jason Ekstrand wrote:
> > > In order to get good performance numbers for this, I had to hack up the
> > > driver to whack wm_prog_d
2017-02-09 18:06 GMT+01:00 Eero Tamminen :
My personal feeling is that minimal merging criteria should be:
> * no known segfaults
>
I bet that glmark2 just does something that's not allowed. Mesa can't
prevent all application bugs? Seems like it has a very buggy history with
lots of segfaults in
On Thursday, February 9, 2017 5:23:47 PM PST Ian Romanick wrote:
[snip]
> Not achieving the desired performance is vastly different from
> segfaults. Does the threaded mode in NVIDIA's driver crash? I'd wager
> not.
Sadly, yes it does. A while back, I tried running some Steam games
on Linux usi
On Wed, Feb 8, 2017 at 6:03 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> src/gallium/include/state_tracker/st_api.h | 19 +++
> src/gallium/state_trackers/dri/dri_context.c| 10 ++
> src/gallium/state_trackers/dri/dri_drawable.c | 6 ++
> src/galli
On 02/09/2017 05:19 PM, Eero Tamminen wrote:
> Hi,
>
> When checking GL errors for "Unturned" (Steam top-20 Unity3D based
> game), I noticed that it uses functions from extension unsupported by
> Mesa, and missing from "features.txt":
> https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_de
On 02/09/2017 05:26 PM, Ian Romanick wrote:
> On 02/09/2017 05:14 PM, Eric Anholt wrote:
>> Ian Romanick writes:
>>
>>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
On 07.02.2017 23:54, Matt Turner wrote:
> On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
>> On Tue, Feb 7, 2017 a
> Okay.. I will add the id member in a later patch to etna_shader
> object. For the moment
> I will pass it as an argument to dump_shader_info(..). Will send a V2
> of that series later the day.
To be honest I think it's nonsense to change this now, if you need an
id in the shader object then add
On 02/09/2017 05:14 PM, Eric Anholt wrote:
> Ian Romanick writes:
>
>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
>>> On 07.02.2017 23:54, Matt Turner wrote:
On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
> On Tue, Feb 7, 2017 at 2:57 AM, Kenneth Graunke
> wrote:
>> On
Hi,
On 09.02.2017 19:14, Eric Anholt wrote:
Ian Romanick writes:
...
No, it absolutely is not fine to merge. We have never allowed such a
thing, and I'll be damned if I'll allow this project to start. Things
that land that are known to be broken never actually get fixed. Then we
have to wa
On 02/09/2017 03:03 PM, Marek Olšák wrote:
> On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick wrote:
>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
>>> On 07.02.2017 23:54, Matt Turner wrote:
On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
> On Tue, Feb 7, 2017 at 2:57 AM, Kenneth Grau
On Thu, Feb 9, 2017 at 12:19 PM, Eero Tamminen
wrote:
> Hi,
>
> When checking GL errors for "Unturned" (Steam top-20 Unity3D based game), I
> noticed that it uses functions from extension unsupported by Mesa, and
> missing from "features.txt":
> https://www.khronos.org/registry/OpenGL/extensions/E
Hi,
When checking GL errors for "Unturned" (Steam top-20 Unity3D based
game), I noticed that it uses functions from extension unsupported by
Mesa, and missing from "features.txt":
https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_debug_label.txt
Could it be added to "features.txt" fi
Ian Romanick writes:
> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
>> On 07.02.2017 23:54, Matt Turner wrote:
>>> On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
On Tue, Feb 7, 2017 at 2:57 AM, Kenneth Graunke
wrote:
> On Monday, February 6, 2017 8:54:40 PM PST Marek Olšák w
On Thu, Feb 9, 2017 at 3:03 PM, Marek Olšák wrote:
> On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick wrote:
>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
>>> On 07.02.2017 23:54, Matt Turner wrote:
On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
> On Tue, Feb 7, 2017 at 2:57 AM, Ken
Hi,
On 09.02.2017 17:03, Marek Olšák wrote:
On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick wrote:
...
No, it absolutely is not fine to merge. We have never allowed such a
thing, and I'll be damned if I'll allow this project to start. Things
that land that are known to be broken never actually
On 02/08/2017 10:01 AM, Jason Ekstrand wrote:
Brian,
While we're on the topic of websites, how do you feel about having it
generated by Sphinx? A couple of people have already gone to the effort
to convert the raw HTML to RST (automatically in the case of release notes).
I guess I don't have
On Thu, Feb 09, 2017 at 09:41:11AM +0100, Juan A. Suarez Romero wrote:
> On Wed, 2017-02-08 at 10:53 -0800, Nanley Chery wrote:
> > On Wed, Feb 08, 2017 at 06:42:44PM +0100, Juan A. Suarez Romero wrote:
> > > On Wed, 2017-02-08 at 09:27 -0800, Nanley Chery wrote:
> > > > On Wed, Feb 08, 2017 at 01:
On 9 February 2017 at 15:23, Matt Turner wrote:
> On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
>> From: Emil Velikov
>>
>> Macro will always be defined as of earlier commit.
>
> How about something like
>
> DRI2DriverPrimeShift was added in dri2proto-2.8, which we now require
> as of the
https://bugs.freedesktop.org/show_bug.cgi?id=99730
--- Comment #3 from Eero Tamminen ---
Thanks! I guess this is one of the use-cases that actually *requires* shader
compiler cache to work, so that user can (on second try) actually exit from the
gfx options. Should I file (a separate) bug about
Hi Eric
2017-02-09 11:59 GMT+01:00 Eric Engestrom :
> On Thursday, 2017-02-09 08:19:39 +0100, Christian Gmeiner wrote:
>> In case ctx->stream == NULL the fail label gets executed where
>> pctx gets dereferenced - too bad pctx is NULL in that case.
>>
>> Caught by Coverity, reported to me by imirki
Hi Lucas
2017-02-09 10:26 GMT+01:00 Lucas Stach :
> Am Mittwoch, den 08.02.2017, 20:47 +0100 schrieb Christian Gmeiner:
>> Hi Lucas,
>>
>> 2017-02-08 12:36 GMT+01:00 Lucas Stach :
>> > Am Mittwoch, den 08.02.2017, 12:10 +0100 schrieb Christian Gmeiner:
>> >> Signed-off-by: Christian Gmeiner
>> >>
Hi all
2017-02-09 13:50 GMT+01:00 Wladimir J. van der Laan :
>> > >> /* shader object, for linking */
>> > >> struct etna_shader {
>> > >> + uint32_t id; /* for debug */
>> > >
>> > > Do you need this? It can certainly be removed from this patch, but I
>> > > don't know if you have other stuff
Allow that capability if the driver indicates that it is supported, and
flag whether images are read-only/write-only in the nir_variable (based
on the NonReadable and NonWritable decorations), which drivers may need
to implement this.
Signed-off-by: Alex Smith
---
src/compiler/spirv/nir_spirv.h
This allows shaders to write to storage images declared with unknown
format if they are decorated with NonReadable ("writeonly" in GLSL).
Previously an image view would always use a lowered format for its
surface state, however when a shader declares a write-only image, we
should use the real form
Hi,
I'm not sure exactly what mechanism you're using to implement the WPE
interfaces, so I'll just list a few options.
Focusing on wpe_renderer_backend_egl_offscreen_target_interface that's
used as the basis for the sharing context and WebGL contexts, the
simplest implementation would just ret
On Thu, Feb 9, 2017 at 3:22 PM, Matt Turner wrote:
> On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
>> From: Emil Velikov
>>
>> The two symbols referenced were introduced with v2.2 and 2.3 of
>> the dri2proto package.
>
> ... and we require dri2proto >= 2.6.
>
> Reviewed-by: Matt Turner
1
On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> Macro will always be defined as of earlier commit.
Same comment as 04/10.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listin
On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> Macro will always be defined as of earlier commit.
How about something like
DRI2DriverPrimeShift was added in dri2proto-2.8, which we now require
as of the previous commit.
_
On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> The two symbols referenced were introduced with v2.2 and 2.3 of
> the dri2proto package.
... and we require dri2proto >= 2.6.
Reviewed-by: Matt Turner
___
mesa-dev mailing l
These all need to go into 17.0
On Feb 8, 2017 06:59, "Samuel Iglesias Gonsálvez"
wrote:
> Signed-off-by: Samuel Iglesias Gonsálvez
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99660
> ---
> src/mesa/drivers/dri/i965/brw_fs_nir.cpp | 15 +--
> 1 file changed, 13 insertio
On Feb 9, 2017 02:23, "Juan A. Suarez Romero" wrote:
On Wed, 2017-02-08 at 13:35 -0800, Jason Ekstrand wrote:
> This fixes the following Vulkan CTS tests on Haswell:
>
> - dEQP-VK.api.image_clearing.clear_color_image.1d_b4g4r4a4_unorm_pack16
> - dEQP-VK.api.image_clearing.clear_color_image.2d_b4g
Reviewed-by: Ian Romanick
On 02/01/2017 12:20 AM, Matt Turner wrote:
> Previously if you used MESA_GL_VERSION_OVERRIDE=3.3COMPAT, Mesa exposed
> an OpenGL 3.3 compatibility profile context (with various unimplemented
> features and bugs), but still refused to compile shaders with
>
>#version
On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick wrote:
> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
>> On 07.02.2017 23:54, Matt Turner wrote:
>>> On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
On Tue, Feb 7, 2017 at 2:57 AM, Kenneth Graunke
wrote:
> On Monday, February 6, 201
On 7 December 2016 at 23:58, Tim Rowley wrote:
> ---
> .../drivers/swr/rasterizer/common/formats.cpp | 104
> ++---
> .../drivers/swr/rasterizer/common/formats.h| 7 +-
> .../drivers/swr/rasterizer/core/format_traits.h| 90 +-
Tim, these three s
On 8 February 2017 at 11:27, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom
> ---
> docs/download.html | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/docs/download.html b/docs/download.html
> index e90c1bbbf2..1cbfded575 100644
> --- a/docs/download.html
> +++ b/docs/dow
On 8 February 2017 at 11:27, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom
> ---
>
> Do we want to list all the modules under src/ ?
> The current list seems a bit arbitrary:
> src/- source code for libraries
> src/mesa- sources for the main Mesa library and device dri
Thanks Brian,
A couple of small additions below, if you've not pushed the series.
On 8 February 2017 at 19:31, Brian Paul wrote:
> +http://www.khronos.org/opengles/";>OpenGL ES (versions 1, 2, 3),
> +http://www.khronos.org/opencl/";>OpenCL,
http://www.khronos.org/openmax/";>OpenMAX,
> +https:/
It will return the current variable ('var') or the earlier declaration
('earlier') in
case of redeclaration of that variable.
In order to distinguish between both, 'is_redeclaration' boolean will indicate
in which
case we are.
Signed-off-by: Samuel Iglesias Gonsálvez
---
This can be merged wi
The get_variable_being_redeclared() function can free 'var' because
a re-declaration of an unsized array variable can establish the size, so
we set the array type to the 'earlier' declaration and free 'var' as it is
not needed anymore.
However, the same 'var' is referenced later in ast_declarator_
On Thu, 2017-02-09 at 13:34 +0100, Ian Romanick wrote:
> NAK.
>
> The way the code is currently architected, if earlier is non-NULL,
> var
> should not be used. There are quite a few places where the callees
> do
> things like 'const glsl_type *const t = (earlier == NULL) ? var->type
> :
> earli
https://bugs.freedesktop.org/show_bug.cgi?id=99730
--- Comment #2 from Grigori Goronzy ---
> At least on Intel SKL with latest Mesa, something weird happens when
> switching between gfx quality levels. Trying e.g. to switch to "Very high"
> level (by exiting the video options with ESC) freezes
Hi Ben,
On 19 January 2017 at 01:44, Ben Crocker wrote:
> Reenable the PPC64LE Vector-Scalar Extension for LLVM versions >= 3.8.1,
> now that LLVM bug 26775 and its corollary, 25503, are fixed.
>
> Amendment: remove extraneous spaces in macro def & invocations.
>
> We would prefer a runtime check
Patches 1, 2, and 4 are
Reviewed-by: Ian Romanick
I sent some comments on patch 3, and I'll leave review of the Gallium
patches to people who actually know Gallium. :)
On 02/08/2017 01:42 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> ---
> src/mesa/main/bufferobj.c | 66
> +++
Hi Ben,
On 19 January 2017 at 01:43, Ben Crocker wrote:
> If llvm::sys::getHostCPUName() returns "generic", override
> it with "pwr8" (on PPC64LE).
>
> This is a work-around for a bug in LLVM: a table entry for "POWER8NVL"
> is missing, resulting in (big-endian) "generic" being returned on
> litt
On 9 February 2017 at 08:07, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Drop all -m*, -W*, -O*, -g* and -f* flags, with the exception of
> -fno-rtti, which must be used if it's part of the llvm-config --cxxflags
> output. We don't want LLVM to dictate the flags we use, and it can even
> cause
From: Emil Velikov
Signed-off-by: Emil Velikov
---
src/mesa/drivers/x11/fakeglx.c | 6 --
src/mesa/drivers/x11/glxapi.c | 20
2 files changed, 26 deletions(-)
diff --git a/src/mesa/drivers/x11/fakeglx.c b/src/mesa/drivers/x11/fakeglx.c
index 394800f02e..d2a099f9a2 10
From: Emil Velikov
Signed-off-by: Emil Velikov
---
src/gallium/state_trackers/glx/xlib/glx_api.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/src/gallium/state_trackers/glx/xlib/glx_api.c
b/src/gallium/state_trackers/glx/xlib/glx_api.c
index 1c541b76db..642ece7b0f 100644
--- a/src/
1 - 100 of 146 matches
Mail list logo
