<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Implement 'scalar_storage_order' attribute"
href="https://bugs.llvm.org/show_bug.cgi?id=35293">35293</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Implement 'scalar_storage_order' attribute
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Frontend
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>anatol.pomozov@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>It is a follow-up for this maillist thread
<a href="http://lists.llvm.org/pipermail/cfe-dev/2017-November/055934.html">http://lists.llvm.org/pipermail/cfe-dev/2017-November/055934.html</a>
There are some protocols (PCI, network, ...) that specify endianness used. To
make the code portable developers need to use some kind of byte swapping
function (such as __builtin_bswapXX) every time accessing the data. Handling it
manually is error-prone. It would be much more convenient to have an attribute
that specifies the field/struct endianness and lets compiler to do byte
swapping when needed.
GCC 6 added attribute called 'scalar_storage_order' that does this (see
<a href="https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Common-Type-Attributes.html#Common-Type-Attributes">https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Common-Type-Attributes.html#Common-Type-Attributes</a>).
It would be great if Clang supported this attribute.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>