<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Regression in Mesa 17 on s390x (zSystems)" href="https://bugs.freedesktop.org/show_bug.cgi?id=100613#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Regression in Mesa 17 on s390x (zSystems)" href="https://bugs.freedesktop.org/show_bug.cgi?id=100613">bug 100613</a> from <a class="email" href="mailto:halfline@gmail.com" title="Ray Strode <halfline@gmail.com>"> Ray Strode</a> <pre>(mid-air collision) (In reply to Roland Scheidegger from <a href="show_bug.cgi?id=100613#c22">comment #22</a>) > I think this has more to do with packed formats - for things like 10/10/10/2 > you can't really access that as multiple individual bytes. Ah, yea, actually if I scroll down a little in the editor I see it gives an example of each case (8/24 for the first case, and 5/5/5/1 for the second case). > Maybe the logic should be simplified for soa fetch for big-endian (e.g. > always use scalars or vectors). Whatever works (well ideally you'd use what > generates better code but I have no idea there on big endian or specifically > ppc boxes.) Yea, I guess thinking about it more, even if we can get scalar fetch to work with sufficient twiddling, that twiddling probably introduces extra operations per element, so maybe not a good idea. I guess we should take another crack at <a href="attachment.cgi?id=131000" name="attach_131000" title="patch that didn't help at all">attachment 131000</a> <a href="attachment.cgi?id=131000&action=edit" title="patch that didn't help at all">[details]</a> <a href='page.cgi?id=splinter.html&bug=100613&attachment=131000'>[review]</a> first.</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>