From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Kettenis <kettenis@chello.nl>
To: schwab@suse.de
Cc: msnyder@redhat.com, cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC/RFA] Print in-memory struct return values
Date: Sun, 16 May 2004 10:28:00 -0000
Message-id: <200405161028.i4GASchl002479@elgar.kettenis.dyndns.org>
References: <200405071707.i47H7kG5071172@elgar.kettenis.dyndns.org> <409C0F30.4090409@gnu.org> <200405081958.i48Jw3dm000345@elgar.kettenis.dyndns.org> <40A26312.7060109@redhat.com> <200405152125.i4FLPr7E000952@elgar.kettenis.dyndns.org> <jead09xru0.fsf@sykes.suse.de>
X-SW-Source: 2004-05/msg00461.html

   From: Andreas Schwab <schwab@suse.de>
   Date: Sun, 16 May 2004 00:12:39 +0200

   Mark Kettenis <kettenis@chello.nl> writes:

   >From the 68000 supplement:

       Functions Returning Structures or Unions

       As mentioned above, when a function returns a structure or union, it
       expects the caller to provide space for the return value and to place
       its address in register %a0.  Having the caller supply the return
       object's space allows re-entrancy.

       A function returning a structure or union also sets %a0 to the value
       it finds in %a0.  Thus when the caller receives control again, the
       address of the returned object resides in register %a0.  ...

Thanks Andreas.  That was what I was looking for.  Michael, are you
aware of any ABI documentation for the not-quite-SVR4 embedded m68k
targets?  Are those GCC only?

Mark