<html><body><p><tt>jgroff@apple.com wrote on 2016-03-22 02:37:47 PM:<br><br>> The runtime functions are hacked in various unsavory ways to give <br>> them Swift-like calling conventions. Many of them also have <br>> important semantics that the compiler needs to be aware of, so if <br>> they aren't exported as standard library API in some way, you really<br>> shouldn't interact with them directly. <br>> (swift_class_getInstanceExtents happens to be OK, but what are you <br>> trying to do with it?)</tt><br><br><tt>I am trying to build Swift on a different architecture (s390x). This</tt><br><tt>function was causing crashes due to the ABI mismatch, and I also</tt><br><tt>found that the issue is not 100% fixed on x86 either, so I wondered</tt><br><tt>if the community has an opinion on the right way to deal with this</tt><br><tt>in the runtime, or if the answer is simply "don't do this for</tt><br><tt>3-scalar returns".</tt><br><br><tt>Thanks, Bryan</tt><BR>
</body></html>