About the 16byte alignment, of 4floats, its mostlikely for SSE :)<br><br><div class="gmail_quote">On 18 October 2010 04:16, Denis Koroskin <span dir="ltr"><<a href="mailto:2korden@gmail.com">2korden@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5">On Mon, 18 Oct 2010 06:00:49 +0400, Walter Bright <<a href="mailto:newshound2@digitalmars.com" target="_blank">newshound2@digitalmars.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a href="http://www.digitalmars.com/d/2.0/attribute.html#align" target="_blank">http://www.digitalmars.com/d/2.0/attribute.html#align</a><br>
<br>
Over time, it has become clear to me that there are only two useful alignments:<br>
<br>
align // set to whatever the C ABI alignment is<br>
align(1) // pack everything in, no alignment padding<br>
<br>
I think any other alignments should be deprecated. Note that with align(1), any alignment is achievable simply by adding in byte fields where desired.<br>
</blockquote>
<br></div></div>
On some platforms it is desired to align struct Vec { float[4] data; } on 16 bytes. I don't recall why now, but I know for sure we do that for all platforms (other than PC maybe). I guess that has something to do with vector operations.<br>
<br>
Bikeshed note: how about align(C) to be consistent with both align(1) and extern(C)?<br>
</blockquote></div><br><br clear="all"><br>-- <br>// Yours sincerely<br>// Emil 'Skeen' Madsen<br>