<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Shader Disk Cache 32/64 bit detection has a flaw. Missed existence of x32 ABI" href="https://bugs.freedesktop.org/show_bug.cgi?id=100073#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Shader Disk Cache 32/64 bit detection has a flaw. Missed existence of x32 ABI" href="https://bugs.freedesktop.org/show_bug.cgi?id=100073">bug 100073</a> from <a class="email" href="mailto:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> Timothy Arceri</a> <pre>(In reply to Darren Salt from <a href="show_bug.cgi?id=100073#c2">comment #2</a>) > This code is intended to be generic; it SHOULD work for other pairs such as > armel and aarch64 (though breakage will happen should you have more than one > 32-bit ARM ABI in use on one system). It's not really breakage, its just that the 32-bit cache would get deleted should you be switching between different Mesa builds. > As such, as it's written, it should > not be testing __i386__, __x86_64__ or similar macros, but it does need to > test __ILP32__. > > (Aside: x32 code is 64-bit.) > > Without optimisation, yes, the testing is effectively at run-time; however, > the values are constant. So in that sense, it's a small amount of bloat and > unreachable code. > Yeah and it's tested once at screen creation so it's not even worth worrying about.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>