<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Sep 14, 2015 at 5:42 PM, Rafael Espíndola <span dir="ltr"><<a href="mailto:rafael.espindola@gmail.com" target="_blank">rafael.espindola@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 14 September 2015 at 20:38, Rui Ueyama via llvm-commits<br>
<span class=""><<a href="mailto:llvm-commits@lists.llvm.org">llvm-commits@lists.llvm.org</a>> wrote:<br>
> That's really good point, we probably should use ulittle32_t instead.<br>
> Regarding alignment, don't we guarantee that the in-memory object we are<br>
> building aligned properly?<br>
<br>
</span>The object we are building is aligned, but the type doesn't know that.<br></blockquote><div><br></div><div>What do you mean? Are you suggesting that we should use aligned_ulittle32_t instead of ulittle32_t to avoid byte swapping overhead in cross-linking use case? </div></div></div></div>