<div dir="ltr">Quick response to a detail, I'll respond to more of this when i have more time.<br><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 7, 2018 at 1:55 PM David Woodhouse <<a href="mailto:dwmw2@infradead.org">dwmw2@infradead.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK... which __x86_indirect_thunk* symbols *are* being used by Clang in<br>
32-bit mode?</blockquote><div><br></div><div>__x86_indirect_thunk</div><div>__x86_indirect_thunk_eax</div><div>__x86_indirect_thunk_ecx</div><div>__x86_indirect_thunk_edx</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I've added __x86_indirect_thunk for 32-bit now, and if<br>
that's *all* the Clang is using then I'll possibly switch GCC into that<br>
mode too.<br>
<br>
Can you take care of filing the tickets for %V0 and "=q"<br>
and attribute__((indirect_branch("keep"))) please? With those fixed, I<br>
think we should be OK again.</blockquote></div></div>