On Fri, Aug 11, 2017 at 3:09 AM, Timothy Arceri <tarc...@itsqueeze.com> wrote:
> On 11/08/17 05:57, Marek Olšák wrote:
>>
>> From: Marek Olšák <marek.ol...@amd.com>
>>
>> ---
>> src/gallium/drivers/radeon/r600_pipe_common.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/src/gallium/drivers/radeon/r600_pipe_common.c
>> b/src/gallium/drivers/radeon/r600_pipe_common.c
>> index 95458d2e..0038c9a 100644
>> --- a/src/gallium/drivers/radeon/r600_pipe_common.c
>> +++ b/src/gallium/drivers/radeon/r600_pipe_common.c
>> @@ -878,21 +878,21 @@ static void r600_disk_cache_create(struct
>> r600_common_screen *rscreen)
>> #endif
>> if (res != -1) {
>> /* These flags affect shader compilation. */
>> uint64_t shader_debug_flags =
>> rscreen->debug_flags &
>> (DBG_FS_CORRECT_DERIVS_AFTER_KILL |
>> DBG_SI_SCHED |
>> DBG_UNSAFE_MATH);
>> rscreen->disk_shader_cache =
>> -
>> disk_cache_create(r600_get_family_name(rscreen),
>> +
>> disk_cache_create(r600_get_llvm_processor_name(rscreen->family),
>
>
> I take it this will always by more fine grained than any compilation options
> for the GLSL/TGSI stages?
>
> Otherwise maybe we should store both like we do for the Mesa/LLVM build
> timestamps.
I don't understand.
Marek
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
