<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Feb 20, 2013, at 6:24 PM, Richard Smith <<a href="mailto:richard@metafoo.co.uk">richard@metafoo.co.uk</a>> wrote:</div><blockquote type="cite">On Wed, Feb 20, 2013 at 6:18 PM, John McCall <span dir="ltr"><<a href="mailto:rjmccall@apple.com" target="_blank">rjmccall@apple.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Feb 20, 2013, at 6:13 PM, Peter Collingbourne <<a href="mailto:peter@pcc.me.uk">peter@pcc.me.uk</a>> wrote:<br>
> <a href="http://llvm-reviews.chandlerc.com/D443" target="_blank">http://llvm-reviews.chandlerc.com/D443</a><br>
<br>
Are you sure we actually *want* to expose this to users?</blockquote><div><br></div><div>I would like to mark the UBSan runtime handler functions as __attribute__((coldcc)), and I think that would make sense for other sanitizers too.</div>
</div>
</blockquote></div><br><div>Are we now willing to commit to a fixed ABI for coldcc? I thought we hadn't been.</div><div><br></div><div>John.</div></body></html>