Change the calling conventions for unboxed tuples slightly
authorSimon Marlow <marlowsd@gmail.com>
Mon, 28 Jul 2008 15:56:21 +0000 (15:56 +0000)
committerSimon Marlow <marlowsd@gmail.com>
Mon, 28 Jul 2008 15:56:21 +0000 (15:56 +0000)
commit02620e7c705ac946db43e61988ca3781af3f2447
tree4a65b034fdda5ed683d951a786b56383b1300e77
parent4ddcff11bae7e4c66c3c895b277eb8b2230aea67
Change the calling conventions for unboxed tuples slightly
When returning an unboxed tuple with a single non-void component, we
now use the same calling convention as for returning a value of the
same type as that component.  This means that the return convention
for IO now doesn't vary depending on the platform, which make some
parts of the RTS simpler, and fixes a problem I was having with making
the FFI work in unregisterised GHCi (the byte-code compiler makes
some assumptions about calling conventions to keep things simple).
compiler/codeGen/CgCallConv.hs
rts/Exception.cmm
rts/PrimOps.cmm
rts/RaiseAsync.c
rts/Schedule.c
rts/StgStartup.cmm