[Mesa-dev] [Bug 100073] Shader Disk Cache 32/64 bit detection has a flaw. Missed existence of x32 ABI

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=100073

--- Comment #26 from oiaohm at gmail.com ---
(In reply to Grazvydas Ignotas from comment #23)
> (In reply to oiaohm from comment #21)
> > This is why I am so upset.   As soon as this comes though I have possible
> > trouble with miss matched mesa versions crossing with each other in a cache
> > directory and being hard to debug.
> That will only happen if you force the same modify timestamp on several
> variations of mesa that are built for matching pointer size. Do you really
> think it's likely to happen in practice?
> 
https://packages.debian.org/stretch/mesa-utils
>From here download the amd64 and the arm64 check timestamps on the files and
they are absolutely identical timestamped.

In fact you can pick any arch in the list there and they are all 23 December
2016 at 1:58 I could go right to the second identical.

Yes it really happens in practice today.  If you go download all the mesa parts
from debian in testing unless there is a patch difference they are all
identical timestamps on the files.   So it 100 percent for sure going to happen
to me a Debian user who uses multiarch fairly completely.   Now other users of
other distributions as those become reproducible could be facing the same
problem.

I have said no to file or build timestamp enough times.  Hopefully now people
will get it that as a option to split versions in the real world is no longer
valid.   Depending on file or build timestamp is depending on those packaging
to use different time what they are not required to-do and have to tools not
to-do.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170311/34353d0e/attachment.html>