<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 22, 2013 at 7:56 AM, Steven Newbury <span dir="ltr"><<a href="mailto:steve@snewbury.org.uk" target="_blank">steve@snewbury.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, 2013-08-22 at 15:22 +0100, Steven Newbury wrote:<br>
> This patch is still not creating elf32_x86_64 objects. No idea<br>
> why. :( It does however, fix elf_x86_64 (-m64) code generation on x32<br>
> hosts which is nice. :)<br>
<br>
</div>I know why. I had assumed Michael Liao (the original patch author) had<br>
submitted all the _LLVM_ x32 support as separate patches, and it was<br>
just the tests/Clang/compiler-rt support that was missing. It seems not<br>
so. Those specific patches he did submit got commited, but many pieces<br>
are missing... I should NEVER make such big assumptions!<br>
<br>
Looks like I'm going to have to go through the original patch and create<br>
a new patch series.<br>
<br>
If I'm going to submit the Clang patch, how should it be submitted? One<br>
patch with what's required to get x32 host to work, then another<br>
enabling x32 code generation once the required changes to llvm are<br>
merged? Would that be sufficient?<br></blockquote><div><br></div><div>Please note that the bulk of work to make Clang x32-capable is in LLVM. The patches sent by Michael a while back no longer apply because we upstreamed some things since then, but the support is not complete yet (mainly in SelDAG). Please be sure to go over the mailing list archives discussing x32, as well as look at the SVN logs for everything mentioning x32. There's quite a bit of history here and it's important to have a full grasp of things.</div>
<div><br></div><div>Eli</div><div><br></div><div><br></div><div> </div></div></div></div>