<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 29, 2013, at 7:38 PM, Richard Smith wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On Thu, Aug 29, 2013 at 6:12 PM, Reid Kleckner <span dir="ltr"><<a href="mailto:rnk@google.com" target="_blank">rnk@google.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im">On Thu, Aug 29, 2013 at 6:11 PM, Richard Smith <span dir="ltr"><<a href="mailto:richard@metafoo.co.uk" target="_blank">richard@metafoo.co.uk</a>></span> wrote:<br></div><div class="gmail_extra">
<div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'd prefer that the ms_abi and sysv_abi attributes are instead mapped to different calling conventions on different targets (so we never use CC_X86_64SysV in cases where it is the same as CC_C).</div>
</blockquote><div><br></div></div><div>I believe the last patch implements that.</div></div></div></div></blockquote><div><br></div><div>Hmm, maybe I'm looking at the wrong patch then. The patch that I'm looking at always maps AT_MSABI to CC_X86_64Win64, then does a fixup from that to CC_C in checkCallingConvention for some targets.</div></div></div></div></blockquote>Heh. :)</div><div><br></div><div>I think I know what he's talking about. Something like this, maybe?</div><div><br></div><div>Chip</div><div></div></body></html>