On Thu, Mar 2, 2017 at 5:36 PM, Mike Lothian <m...@fireburn.co.uk> wrote: > I'm guessing when the code runs the 32bit and 64bit have different build > times so invalidate the cache and create a new one > > On Thu, 2 Mar 2017 at 16:25 Marek Olšák <mar...@gmail.com> wrote: >> >> On Thu, Mar 2, 2017 at 3:03 PM, Mike Lothian <m...@fireburn.co.uk> wrote: >> > Is this because the 32bit and 64bit versions have slightly different >> > time >> > stamps used in the cache directory name? I was under the impression that >> > the >> > cache itself could be shared between 32bit & 64bit? >> > >> > I guess this only matters for the few games that offer both a 32bit and >> > 64bit binary, producing duplicate entries in both caches potentially >> >> In addition to that, I'd like to know why the CPU architecture is even >> being considered. IMO, the CPU arch can be ignored for the shader >> cache completely.
Clearing the cache completely would be unwise. Why not just delete the oldest entries like any other cache would do. Marek _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
