On 06/22/2017 01:54 AM, Marek Olšák wrote:
On Tue, Jun 20, 2017 at 10:56 PM, Samuel Pitoiset
wrote:
On 06/20/2017 10:53 PM, Samuel Pitoiset wrote:
I have just tested this patch with Hero Siege, it still crashes.
As you said, it's definitely a multithreading issue because it crashes
diffe
On Tue, Jun 20, 2017 at 10:56 PM, Samuel Pitoiset
wrote:
>
>
> On 06/20/2017 10:53 PM, Samuel Pitoiset wrote:
>>
>> I have just tested this patch with Hero Siege, it still crashes.
>>
>> As you said, it's definitely a multithreading issue because it crashes
>> differently all the time.
>>
>> Let m
On 06/20/2017 10:53 PM, Samuel Pitoiset wrote:
I have just tested this patch with Hero Siege, it still crashes.
As you said, it's definitely a multithreading issue because it crashes
differently all the time.
Let me know if you need more information.
FWIW, "Peace, Death!" and "Riptale" [1
I have just tested this patch with Hero Siege, it still crashes.
As you said, it's definitely a multithreading issue because it crashes
differently all the time.
Let me know if you need more information.
On 06/19/2017 01:40 PM, Nicolai Hähnle wrote:
From: Nicolai Hähnle
si_build_shader_var
Reviewed-by: Marek Olšák
Marek
On Mon, Jun 19, 2017 at 1:40 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> si_build_shader_variant can actually be called directly from one of
> normal-priority compiler threads. In that case, the thread_index is
> only valid for the normal tm array.
>
> v
From: Nicolai Hähnle
si_build_shader_variant can actually be called directly from one of
normal-priority compiler threads. In that case, the thread_index is
only valid for the normal tm array.
v2:
- use the correct sel/shader->compiler_ctx_state
Bugzilla: https://bugs.freedesktop.org/show_bug.c
On Mon, Jun 12, 2017 at 11:26 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> si_build_shader_variant can actually be called directly from one of
> normal-priority compiler threads. In that case, the thread_index is
> only valid for the normal tm array.
>
> Bugzilla: https://bugs.freedesktop
From: Nicolai Hähnle
si_build_shader_variant can actually be called directly from one of
normal-priority compiler threads. In that case, the thread_index is
only valid for the normal tm array.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101384 (maybe)
Fixes: 86cc8097266c ("radeonsi: u
