From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Nathan Sidwell <nathan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [m68k] fix return value extraction
Date: Tue, 06 Jun 2006 12:31:00 -0000 [thread overview]
Message-ID: <20060606123044.GA23121@nevyn.them.org> (raw)
In-Reply-To: <jebqt68sn2.fsf@sykes.suse.de>
On Tue, Jun 06, 2006 at 12:50:41PM +0200, Andreas Schwab wrote:
> Nathan Sidwell <nathan@codesourcery.com> writes:
>
> > + /* a.out */
> > +
> > + void
> > + m68k_aout_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
> > + {
> > + struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
> > +
> > + set_gdbarch_return_value (gdbarch, m68k_return_value);
> > +
> > + /* aout uses %a1 */
> > + tdep->struct_value_regnum = M68K_A1_REGNUM;
> > + tdep->struct_return = reg_struct_return;
> > + /* Pointers are returned in %a0 */
> > + tdep->ptr_value_regnum = M68K_A0_REGNUM;
>
> I don't think this is correct. The GCC default for m68k is the old Sun3
> ABI, which returns everything in %d0 and uses pcc structure return.
Ah - sort of, but not. I spent a while last week disecting the
configuration defaults when Nathan asked me about this. In fact, while
m68k.h defaults to pcc structure return, the "embedded" configurations
all turn it right back off again - including m68k-aout, m68k-coff,
m68k-elf, and m68k-rtems. The only thing I saw which definitively used
it was NetBSD ELF.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-06 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 15:26 Nathan Sidwell
2006-06-05 16:51 ` Andreas Schwab
2006-06-06 10:18 ` Nathan Sidwell
2006-06-06 10:50 ` Andreas Schwab
2006-06-06 12:31 ` Daniel Jacobowitz [this message]
2006-06-17 12:54 ` Andreas Schwab
2006-06-09 10:13 ` Andreas Schwab
2006-06-09 10:15 ` Nathan Sidwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060606123044.GA23121@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nathan@codesourcery.com \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox