Recent commits introduced new unused variable warnings, fix them.
---
src/gallium/drivers/radeon/radeon_uvd.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/gallium/drivers/radeon/radeon_uvd.c
b/src/gallium/drivers/radeon/radeon_uvd.c
index 16ee541..81f3f45 100644
Otherwise we get:
warning: 'num_user_sgprs' may be used uninitialized in this function
...
---
src/gallium/drivers/radeonsi/si_shader.c| 2 +-
src/gallium/drivers/radeonsi/si_state_shaders.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
On Tue, Aug 18, 2015 at 11:30 AM, Christian König
deathsim...@vodafone.de wrote:
On 18.08.2015 01:51, Grazvydas Ignotas wrote:
Recent commits introduced new unused variable warnings, fix them.
Reviewed-by: Christian König christian.koe...@amd.com
Do you have commit access?
No, it's only
Similarly to scissor states, we can use single atom to track all viewport
states. This will allow to simplify dirty atom handling later.
---
src/gallium/drivers/r600/evergreen_state.c | 7 ++---
src/gallium/drivers/r600/r600_blit.c | 2 +-
src/gallium/drivers/r600/r600_hw_context.c
There doesn't seem any reason to start from 4.
Start from 1 instead (0 is left reserved to catch uninitialized atoms).
---
src/gallium/drivers/r600/evergreen_state.c | 2 +-
src/gallium/drivers/r600/r600_pipe.h | 2 +-
src/gallium/drivers/r600/r600_state.c | 2 +-
3 files changed, 3
As suggested by Marek Olšák, we can use single atom to track all scissor
states. This will allow to simplify dirty atom handling later.
---
src/gallium/drivers/r600/evergreen_state.c | 33 ++---
src/gallium/drivers/r600/r600_blit.c | 2 +-
Now that R600_NUM_ATOMS is below 64, dirty atom tracking can be
simplified.
---
src/gallium/drivers/r600/r600_pipe.h | 41 ++--
1 file changed, 11 insertions(+), 30 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_pipe.h
r600 currently has 73 atoms and looping through their dirty flags has
become costly because checking each flag requires a pointer
dereference before the read. To avoid having to do that add additional
bitfield which can be checked really quickly thanks to tzcnt instruction.
id field was added to
This is analogous to r300_mark_atom_dirty() used by r300, and will
be used by later patches. For common radeon code, appropriate helper
is called through a function pointer.
No functional changes.
---
src/gallium/drivers/r600/evergreen_compute.c| 2 +-
On evergreen config_state is not used, so don't mark it dirty.
---
src/gallium/drivers/r600/r600_hw_context.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r600/r600_hw_context.c
b/src/gallium/drivers/r600/r600_hw_context.c
index d67fdfd..c048a71
Instead of writing to rctx-atoms directly use a helper to take
advantage of assert checks.
---
src/gallium/drivers/r600/evergreen_state.c | 4 ++--
src/gallium/drivers/r600/r600_pipe.h | 1 +
src/gallium/drivers/r600/r600_state.c| 4 ++--
marek.ol...@amd.com
Marek
On Sun, Aug 9, 2015 at 11:42 PM, Grazvydas Ignotas nota...@gmail.com wrote:
r600 currently has 73 atoms and looping through their dirty flags has
become costly because checking each flag requires a pointer
dereference before the read. To avoid having to do that add
Hi,
On Thu, Oct 29, 2015 at 6:21 PM, Emil Velikov wrote:
> On 29 October 2015 at 15:22, Emmanuel Gil Peyrot
> wrote:
>> This was causing compilation issues when one of its providers wasn’t
>> already included before gbm.h.
> Cc: "11.0"
On Sun, Aug 30, 2015 at 10:11 PM, Marek Olšák mar...@gmail.com wrote:
...
diff --git a/src/gallium/drivers/radeonsi/si_state_draw.c
b/src/gallium/drivers/radeonsi/si_state_draw.c
index 2ff58d1..81575b5 100644
--- a/src/gallium/drivers/radeonsi/si_state_draw.c
+++
On Sun, Aug 30, 2015 at 10:12 PM, Marek Olšák mar...@gmail.com wrote:
From: Marek Olšák marek.ol...@amd.com
This is always false on amdgpu (set by calloc).
---
src/gallium/drivers/radeon/radeon_winsys.h| 1 +
src/gallium/winsys/radeon/drm/radeon_drm_cs.c | 4 +---
Hi,
On Sun, Aug 30, 2015 at 10:11 PM, Marek Olšák mar...@gmail.com wrote:
The viewport and scissor states are optimized. The main thing is that setting
non-zero viewports and scissors is delayed until a shader that writes
VIEWPORT_INDEX appears (which is typically never).
...
Radeonsi no
Similarly to scissor states, we can use single atom to track all viewport
states. This will allow to simplify dirty atom handling later.
---
v2: rebased, moved dirty_mask set out of the loop
src/gallium/drivers/r600/evergreen_state.c | 7 ++---
src/gallium/drivers/r600/r600_blit.c |
It's no longer used by both r600 and radeonsi now.
---
src/gallium/drivers/r600/r600_pipe.h | 2 --
src/gallium/drivers/r600/r600_state_common.c | 1 -
src/gallium/drivers/radeon/r600_pipe_common.h | 3 +--
src/gallium/drivers/radeonsi/si_state.c | 1 -
4 files changed, 1
There doesn't seem any reason to start from 4.
Start from 1 instead (0 is left reserved to catch uninitialized atoms).
---
src/gallium/drivers/r600/evergreen_state.c | 2 +-
src/gallium/drivers/r600/r600_pipe.h | 2 +-
src/gallium/drivers/r600/r600_state.c | 2 +-
3 files changed, 3
As suggested by Marek Olšák, we can use single atom to track all scissor
states. This will allow to simplify dirty atom handling later.
---
v2: rebased, moved dirty_mask set out of the loop
src/gallium/drivers/r600/evergreen_state.c | 36 ++
Now that R600_NUM_ATOMS is below 64, dirty atom tracking can be
simplified.
---
src/gallium/drivers/r600/r600_hw_context.c | 9 +++---
src/gallium/drivers/r600/r600_pipe.h | 45
src/gallium/drivers/r600/r600_state_common.c | 9 +++---
3 files changed, 14
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.
---
src/gallium/drivers/r600/r600_state.c| 22 +-
to all scissors, not just 0. That is, if scissor.enable is changed,
all scissors must be marked as dirty.
Marek
On Mon, Aug 24, 2015 at 2:24 AM, Grazvydas Ignotas nota...@gmail.com wrote:
As suggested by Marek Olšák, we can use single atom to track all scissor
states. This will allow to simplify
On Thu, Sep 10, 2015 at 5:35 AM, Michel Dänzer <mic...@daenzer.net> wrote:
> On 10.09.2015 01:33, Grazvydas Ignotas wrote:
>> "r600g: apply disable workaround on all scissors" forgot to update
>> num_dw, fix it.
>>
>> Fixes: fbb423b433 "r600g: apply
"r600g: apply disable workaround on all scissors" forgot to update
num_dw, fix it.
Fixes: fbb423b433 "r600g: apply disable workaround on all scissors"
Reported-and-tested-by: Markus Trippelsdorf
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91921
---
"r600g: apply disable workaround on all scissors" forgot to update
num_dw, fix it.
Fixes: fbb423b433 "r600g: apply disable workaround on all scissors"
Reported-and-tested-by: Markus Trippelsdorf <mar...@trippelsdorf.de>
Signed-off-by: Grazvydas Ignotas <nota...@gmail.
Hi,
On Fri, Dec 4, 2015 at 6:19 AM, Dave Airlie <airl...@gmail.com> wrote:
> Hey all,
>
> I've pushed an updated version of the r600g tess support to my
> r600g-tess-submit branch.
FWIW:
Tested-by: Grazvydas Ignotas <nota...@gmail.com>
on JUNIPER XT with heaven and p
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92229
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
Only tested on Juniper, but I guess others will need this too.
src/gallium/drivers/r600/evergreen_state.c | 2 +-
src/gallium/drivers/r600/r600_state.c | 2 +-
2 files chang
On Tue, Dec 22, 2015 at 5:37 PM, Nicolai Hähnle <nhaeh...@gmail.com> wrote:
> On 21.12.2015 21:12, Grazvydas Ignotas wrote:
>>
>> When buffer size is less than 16, zero ends up being programmed as
>> size, which prevents the hardware from fetching the correct values.
&
I've tried it on AMD JUNIPER (DRM 2.43.0 / 4.6.0) and it does not pass
the kernel CS validator with
[drm:evergreen_packet3_check.isra.14 [radeon]] *ERROR* Packet3 opcode
42 not supported
printed many times.
I guess it needs some kernel patch? I haven't found anything relevant
in Alex's kernel
On Tue, May 31, 2016 at 2:58 AM, Grazvydas Ignotas <nota...@gmail.com> wrote:
> I've patched the CS validator and there seem to be some regressions:
>
> arb_map_buffer_range 11/11 5/11
> copybuffersubdata decrement-offset
> copybuffersubdata increment-offset
> co
h is based on, don't know if it has any effect.
Should I attempt to bisect?
Gražvydas
On Tue, May 31, 2016 at 1:30 AM, Marek Olšák <mar...@gmail.com> wrote:
> On Tue, May 31, 2016 at 12:17 AM, Grazvydas Ignotas <nota...@gmail.com> wrote:
>> I've tried it on AMD JUNIPER (DRM 2.43.
HONY rule and the
> temporary file.
>
> The former is used to ensure that the header is regenerated when on each
> make invocation, while the latter helps us avoid the unneeded rebuild(s)
> when the SHA1 hasn't changed.
>
> Cc: Grazvydas Ignotas <nota...@gmail.com>
>
On Tue, May 31, 2016 at 5:16 PM, Topi Pohjolainen
wrote:
> This INTEL_DEBUG option disables lossless compression (also known
> as render buffer compression).
>
> Suggested-by: Eero Tamminen
> Signed-off-by: Topi Pohjolainen
On Thu, Jun 2, 2016 at 12:44 AM, Jason Ekstrand wrote:
> Signed-off-by: Jason Ekstrand
> Cc: "12.0"
> Cc: Ian Romanick
> ---
> src/intel/vulkan/gen7_pipeline.c | 12 ++--
>
On Wed, Jun 1, 2016 at 9:57 PM, Marek Olšák <mar...@gmail.com> wrote:
> Hi,
>
> This is version 2 of the previous series. This time it's been tested!!
>
> Tested cards:
> - RV670
> - RV730
> - EG/REDWOOD
> - CAYMAN
All good on JUNIPER now (piglit and a few ra
On Mon, May 30, 2016 at 3:46 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> As we'll need the file in the release tarball, rework the rule so that
> the file is regenerated _only_ if we're in a git repository.
>
> With this in place we can
Remove 'reg' option that does not actually exist, elaborate more about
'sync' and add the missing options.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, if this is ok please somebody push
docs/envvars.html | 12 ++--
1 file changed, 10 insertions
Tried this while playing with apitrace and am getting segfaults when
running any trace with a cached (second) run. Not sure if it's "wrong"
traces I've chosen or what, you can take one example from this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=96425
It would also be good idea to hide the
The buffers are referenced from r600_update_driver_const_buffers()
-> r600_set_constant_buffer() -> u_upload_data(), but nothing
ever releases the reference. Similar case with driver_consts.
Found using valgrind.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
No c
On Wed, Feb 17, 2016 at 1:45 AM, Ben Widawsky
wrote:
> The Iris part is left unbranded because we did not have these with original
> SKL.
>
> v2: 0x192d is gt3, not gt4
The name and description still don't agree.
>
> Cc: "11.0 11.1"
On Thu, Mar 10, 2016 at 7:36 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 35
> ++
> 1 file changed, 35 insertions(+)
>
> diff --git
On Fri, Mar 11, 2016 at 7:48 PM, Marek Olšák wrote:
> Can you paste the build failures please?
In file included from compute_memory_pool.c:42:0:
evergreen_compute_internal.h:43:2: error: unknown type name ‘LLVMContextRef’
LLVMContextRef llvm_ctx;
^
evergreen_compute.c: In
Hi,
On Tue, Apr 5, 2016 at 10:30 PM, Jason Ekstrand wrote:
> I know we don't usually do merges in this project, but
> the Vulkan driver is big and has a lot of history that we would like to
> preserve. If you're strongly opposed to doing a merge, please speak up now!
I
On Fri, Apr 15, 2016 at 6:06 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> The __i386__ and __x86-64__ macros are gcc/clang specific, thus one does
> not need the __GNUC__ at the top.
>
> Additionally, having _M_IX86 and _M_X64 in the same
Mark variables MAYBE_UNUSED to avoid unused-but-set-variable warnings
in release build.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/gallium/auxiliary/pipebuffer/pb_buffer_fenced.c | 2 +-
src/gallium/aux
Mark variables MAYBE_UNUSED to avoid unused-but-set-variable warnings
in release build.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/intel/vulkan/anv_dump.c | 2 +-
src/intel/
on both GCC 4.2
(oldest supported by mesa) and clang 3.0 (just some random old version,
nut sure what's the minimum for mesa).
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/util/macros.h | 2 ++
1 file chan
Mark variables MAYBE_UNUSED to avoid unused-but-set-variable warnings
in release build.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/intel/isl/isl.c | 2 +-
src/intel/isl/isl_gen7.c | 2 +-
2 files c
I guess almost everyone here builds mesa with asserts enabled, but many
forget asserts are off by default, so ordinary users get thrown at quite
a lot of warnings. This tries to improve the situation somewhat.
Grazvydas Ignotas (7):
util: add MAYBE_UNUSED for config dependent variables
glsl
Mark variable MAYBE_UNUSED to avoid unused-but-set-variable warning in
release build.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/compiler/spirv/vtn_cfg.c | 2 +-
1 file changed, 1 insertion(+), 1 de
Mark variable MAYBE_UNUSED to avoid unused-but-set-variable warning in
release build.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/compiler/glsl/lower_buffer_access.cpp | 2 +-
1 file changed, 1 insertion
Avoids warnings in release builds.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
src/gallium/auxiliary/gallivm/lp_bld_intr.c | 2 +-
src/gallium/drivers/radeon/radeon_llvm_emit.c | 2 +-
2 files chan
For ctags users like me.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
I have no commit access, if this patch is ok, please someone push.
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index b4f88f7..7db5639 100644
--- a/.gitignore
On Fri, Apr 15, 2016 at 9:46 PM, Christian Schmidbauer
wrote:
> On 15/04/16 17:06, Emil Velikov wrote:
>> From: Emil Velikov
>>
>> The __i386__ and __x86-64__ macros are gcc/clang specific, thus one does
>> not need the __GNUC__ at the top.
On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote:
> On 16 April 2016 at 02:00, Grazvydas Ignotas <nota...@gmail.com> wrote:
>> This is mostly for variables that are only used in asserts and cause
>> unused-but-set-variable warnings in rel
On Sat, Jul 30, 2016 at 6:22 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> for debugging
> ---
> src/gallium/auxiliary/os/os_process.c | 37
> +++
> src/gallium/auxiliary/os/os_process.h | 2 ++
> 2 files changed, 39
On Wed, Jul 13, 2016 at 2:56 AM, Timothy Arceri
<timothy.arc...@collabora.com> wrote:
> On Sat, 2016-07-09 at 20:21 +0300, Grazvydas Ignotas wrote:
>>
>> I think I still have some more:
>> - running 32bit program after 64bit version of the same thing (or
>>
On Tue, Jul 12, 2016 at 11:52 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> This patch may be dropped depending on feedback.
>
> Cc: 12.0
> ---
> src/gallium/drivers/radeonsi/si_shader.c | 33
>
On Mon, Jul 18, 2016 at 3:14 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> src/gallium/auxiliary/os/os_time.c | 15 +--
> src/gallium/auxiliary/os/os_time.h | 4
> 2 files changed, 13 insertions(+), 6 deletions(-)
>
> diff --git
On Sat, Jul 16, 2016 at 2:00 AM, Marek Olšák wrote:
> On Wed, Jul 13, 2016 at 10:50 AM, Vedran Miletić wrote:
>> On 07/13/2016 05:19 AM, Timothy Arceri wrote:
>>>
>>> So I finally got around to setting up my new polaris card on fedora. I
>>> was curious to
On Tue, Jun 28, 2016 at 10:53 AM, Timothy Arceri
<timothy.arc...@collabora.com> wrote:
> On Mon, 2016-06-27 at 00:46 +1000, Timothy Arceri wrote:
>> On Sun, 2016-06-26 at 16:15 +0300, Grazvydas Ignotas wrote:
>> > Tried this while playing with apitrace and am get
On Sat, Jul 9, 2016 at 10:02 AM, Timothy Arceri
<timothy.arc...@collabora.com> wrote:
> On Fri, 2016-07-01 at 14:12 +1000, Timothy Arceri wrote:
>> On Thu, 2016-06-30 at 00:59 +0300, Grazvydas Ignotas wrote:
>> > On Wed, Jun 29, 2016 at 3:11 PM, Timothy Arceri
>> &
On Sat, Jul 9, 2016 at 6:49 PM, Marek Olšák wrote:
> On Fri, Jul 8, 2016 at 3:20 AM, Timothy Arceri
> wrote:
>> On Wed, 2016-06-29 at 18:32 +0200, Marek Olšák wrote:
>>> Hi,
>>>
>>> This series implements basic multithreaded LLVM shader compilation
On Wed, Jun 29, 2016 at 3:11 PM, Timothy Arceri
<timothy.arc...@collabora.com> wrote:
> On Wed, 2016-06-29 at 03:47 +0300, Grazvydas Ignotas wrote:
>> On Tue, Jun 28, 2016 at 10:53 AM, Timothy Arceri
>> <timothy.arc...@collabora.com> wrote:
>> > On Mon, 2016-
Fixes: 97dfff54 ("radv: Dump command buffer on hang.")
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/amd/vulkan/radv_device.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/rad
On Wed, Feb 22, 2017 at 5:45 AM, Timothy Arceri wrote:
> If there was more than a single directory in the .cache/mesa dir
> then it would only remove one (or none) of the directories.
>
> Apparently Valgrind was also reporting:
> Conditional jump or move depends on
So, as there are no better solutions in sight, can somebody please
push this patch?
Gražvydas
On Wed, Feb 15, 2017 at 5:33 AM, Alex Deucher wrote:
> On Tue, Feb 14, 2017 at 10:27 PM, Michel Dänzer wrote:
>> On 14/02/17 08:25 PM, Marek Olšák wrote:
>>>
On Sat, Feb 11, 2017 at 9:58 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> src/gallium/drivers/radeon/r600_query.c | 25
> ++-
> src/gallium/drivers/radeon/r600_query.h | 1 +
>
On Thu, Feb 9, 2017 at 12:06 AM, Timothy Arceri wrote:
> ---
> src/util/disk_cache.c | 25 -
> 1 file changed, 12 insertions(+), 13 deletions(-)
>
> diff --git a/src/util/disk_cache.c b/src/util/disk_cache.c
> index 7691621..edfff73 100644
> ---
They cause regressions on little endian.
Fixes: 172bfdaa9e ("r300g: add support for PIPE_FORMAT_x8R8G8B8_*")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98869
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/gallium/drivers/r300/r3
On Tue, Feb 14, 2017 at 3:12 PM, Haridasan, Sujith
wrote:
> I am using mesa 12.0.1 from yocto project
> (http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/mesa/mesa_12.0.1.bb?h=morty).
> While building core-image-sato ( which is the graphical
On Wed, Feb 15, 2017 at 2:03 AM, Jason Ekstrand wrote:
> ---
> src/util/Makefile.sources | 3 ++-
> src/util/vk_util.h| 43 +++
> 2 files changed, 45 insertions(+), 1 deletion(-)
> create mode 100644 src/util/vk_util.h
>
>
On Mon, Feb 13, 2017 at 10:22 AM, Michel Dänzer <mic...@daenzer.net> wrote:
> On 13/02/17 05:17 PM, Michel Dänzer wrote:
>> On 11/02/17 08:01 AM, Grazvydas Ignotas wrote:
>>> They cause regressions on little endian.
>>>
>>> Fixes: 172bfdaa9e (&qu
If i-th thread could not be created it means we have i threads,
not i+1, because we start from 0.
Fixes: 404d0d5 "gallium/u_queue: add an option to have multiple worker threads"
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/gallium/auxiliary/ut
ns.
Fixes: 4aea8fe "gallium/u_queue: fix random crashes when the app calls exit()"
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/gallium/auxiliary/util/u_queue.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/auxiliary/util/u_queue.
On Wed, Mar 1, 2017 at 7:25 AM, Timothy Arceri wrote:
> ---
> src/util/disk_cache.c | 37 ++---
> 1 file changed, 34 insertions(+), 3 deletions(-)
>
> diff --git a/src/util/disk_cache.c b/src/util/disk_cache.c
> index f5e1145..2a0edca 100644
On Wed, Mar 1, 2017 at 7:25 AM, Timothy Arceri wrote:
> ...
> diff --git a/src/util/disk_cache.c b/src/util/disk_cache.c
> index 2a0edca..03aae02 100644
> --- a/src/util/disk_cache.c
> +++ b/src/util/disk_cache.c
> @@ -30,20 +30,21 @@
> #include
> #include
> #include
On Thu, Mar 2, 2017 at 8:36 AM, Timothy Arceri wrote:
>
>
> On 02/03/17 17:17, Ilia Mirkin wrote:
>>
>> On Thu, Mar 2, 2017 at 1:08 AM, Timothy Arceri
>> wrote:
>>>
>>> Previously we were deleting the entire cache if a user switched
>>> between 32
On Tue, Oct 4, 2016 at 1:09 PM, Nicolai Hähnle wrote:
> On 04.10.2016 03:48, Dave Airlie wrote:
>
> [snip]
>>
>> diff --git a/src/amd/common/ac_llvm_helper.cpp
>> b/src/amd/common/ac_llvm_helper.cpp
>> new file mode 100644
>> index 000..feafdaf
>> --- /dev/null
>> +++
On Tue, Oct 4, 2016 at 3:15 AM, Timothy Arceri
wrote:
> This fixes an unused variable warning on release builds.
> ---
> src/mesa/drivers/dri/i965/brw_fs.cpp | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_fs.cpp
>
On Wed, Nov 9, 2016 at 8:11 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> Port of the anv commit d96345de989 ("anv: Suffix the intel_icd file with
> the host CPU").
I guess the subject of this patch should say radeon_icd instead of
On Mon, Oct 10, 2016 at 2:25 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> The kernel patch has been sent to amd-gfx.
> ---
> src/gallium/drivers/radeonsi/si_compute.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git
Just mark with MAYBE_UNUSED.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/amd/vulkan/radv_cmd_buffer.c | 34 ++
src/amd/vulkan/radv_query.c | 6 +++---
2 files changed, 21 insertions(+), 19 del
Otherwise we get 32bit warnings because handle is plain uint64_t there
and NULL is not suited to initialize that.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/amd/vulkan/radv_meta_blit2d.c | 2 +-
src/amd/vulkan/radv_meta_bufi
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/gallium/drivers/radeonsi/si_blit.c | 2 +-
src/gallium/drivers/radeonsi/si_state.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_bli
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/intel/vulkan/anv_blorp.c | 3 ++-
src/intel/vulkan/genX_cmd_buffer.c | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/intel/vulkan/anv_blorp.c b/src/intel/
Doesn't look like this can work on 32bit, just rids of annoying
warning.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/intel/tools/aubinator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/intel/tools/aubinat
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
src/mesa/drivers/dri/i965/brw_blorp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_blorp.c
b/src/mesa/drivers/dri/i965/brw_blorp.c
index 4c1d858..8b5750c 100644
--- a/sr
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/gallium/drivers/softpipe/sp_state_shader.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/softpipe/sp_state_shader.c
b/src/gallium/drivers/so
Mark some paths unreachable so that compiler knows variables are
initialized in all valid paths.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access, somebody please push
src/amd/common/ac_nir_to_llvm.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
anv_util.c and radv_util.c are essentially duplicates, so create a new
vk_util.c to be shared by both vulkan drivers. Some other content from
anv_private.h and radv_private.h was moved to vk_util.h too.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
config
Emitted on release build in case vk_error() return is not used.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/vulkan/vk_util.c | 4
src/vulkan/vk_util.h | 13 -
2 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/src/vulkan/vk_
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
v2: take Eduardo Lima's suggestion further - remove the variable completely
no commit access
src/mesa/drivers/dri/i965/brw_blorp.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_b
VK_ICD_WSI_PLATFORM_MAX is used, but a duplicate from wsi_common.h .
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
requested by Emil:
https://lists.freedesktop.org/archives/mesa-dev/2017-January/140733.html
src/intel/vulkan/anv_private.h | 15 --
Hi,
just out of the interest, can this be used on Tegra X1 right now?
If so, what would I need to get it to work (kernel, firmware, something else)?
I'd be interested to run mesa on the Shield TV.
Gražvydas
On Fri, Jan 13, 2017 at 9:47 AM, Alexandre Courbot wrote:
> From:
These seem unlikely to be used.
Also remove irrelevant comment about SKL.
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/amd/vulkan/radv_private.h | 15 +--
src/amd/vulkan/radv_util.c| 19 ---
2 files changed, 1 insertion(
Unfortunately this one breaks at least (surprise!) texturecubemap
SaschaWillemsVulkan demo.
I recommend you try it yourself, there are even precompiled binaries
available (see README.md):
https://github.com/SaschaWillems/Vulkan
Gražvydas
On Tue, Jan 10, 2017 at 5:12 PM, Nicolai Hähnle
These seem unlikely to be used.
Also remove irrelevant comment about SKL.
v2: forgot to rebase on master
Signed-off-by: Grazvydas Ignotas <nota...@gmail.com>
---
no commit access
src/amd/vulkan/radv_private.h | 15 +--
src/amd/vulkan/radv_util.c| 19 ---
2
On Thu, Jan 12, 2017 at 12:26 PM, Nicolai Hähnle <nhaeh...@gmail.com> wrote:
> On 12.01.2017 00:58, Grazvydas Ignotas wrote:
>>
>> b838f642 "ac/debug: Move sid_tables.h generation to common code." moved
>> sid_tables.h but forgot the corresponding .gitignore.
&
1 - 100 of 340 matches
Mail list logo