From: Michael Snyder <msnyder@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ping] Re: [RFA] sh-tdep: multi-arch the push_dummy_call method.
Date: Wed, 20 Aug 2003 20:39:00 -0000 [thread overview]
Message-ID: <3F43DC57.4020906@redhat.com> (raw)
In-Reply-To: <16184.16051.841312.312872@localhost.redhat.com>
Elena Zannoni wrote:
> Michael Snyder writes:
> > Michael Snyder wrote:
> >
> > > Elena, this splits off two versions of push_dummy_call: one for sh2e,
> > > sh3e, and sh4, and the other for all the others. There are two
> > > differences:
> > > how they pass floats, and how they pass large structs.
> > >
> > > This wins us 6 new passes in call-ar-st, one in call-rt-st, 13 in
> > > callfuncs,
> > > and one in varargs.
> > >
>
> For which versions do we get more passes? all versions < sh5?
>
> I don't have an abi document, in front of me, you are not just making
> the tests pass, i.e. complying with what gcc thinks the ABI is, right? ;-)
>
>
> ok
Committed.
prev parent reply other threads:[~2003-08-20 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 22:20 Michael Snyder
2003-08-11 23:03 ` [ping] " Michael Snyder
2003-08-12 1:03 ` Elena Zannoni
2003-08-12 22:15 ` Michael Snyder
2003-08-20 20:39 ` Michael Snyder [this message]
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=3F43DC57.4020906@redhat.com \
--to=msnyder@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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