<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c21">Comment # 21</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 <span class="vcard"><a class="email" href="mailto:rstrode@redhat.com" title="Ray Strode [halfline] <rstrode@redhat.com>"> <span class="fn">Ray Strode [halfline]</span></a>
</span></b>
<pre>Unless I'm misunderstanding something, I think this comment in u_format.h is
the crux of the issue:
* If each channel is accessed as an individual N-byte value, X is always•
* at the lowest address in memory, Y is always next, and so on. For all•
* currently-defined formats, the N-byte value has native endianness.•
*•
* If instead a group of channels is accessed as a single N-byte value,•
* the order of the channels within that value depends on endianness.•
* For big-endian targets, X is the most significant subvalue,•
* otherwise it is the least significant one.•
*•
I guess vector fetch is the first paragraph, and scalar fetch is the second
paragraph. So they can't behave the same on big endian unless we introduce
swaps.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>