From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa:ppc] Convert PPC to "return_value"
Date: Thu, 23 Oct 2003 16:11:00 -0000 [thread overview]
Message-ID: <1031023161129.ZM13883@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "[rfa:ppc] Convert PPC to "return_value"" (Oct 20, 7:27pm)
On Oct 20, 7:27pm, Andrew Cagney wrote:
> The attached switches the PPC architectures over to the new
> "return_value" gdbarch method.
I'm still thinking about this one.
The problem that I have with this patch is that I'm not convinced that
it's always desirable to combine the "use struct convention" code
with the code which implements the loading/storing of the return
value.
Due to the way the PPC ABIs are specified, I do happen to like this
approach for PPC. However, I'm not convinced that this is the best
approach for all architectures.
So I'm still mulling it over...
Kevin
next prev parent reply other threads:[~2003-10-23 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 23:27 Andrew Cagney
2003-10-23 16:11 ` Kevin Buettner [this message]
2003-11-06 20:43 ` Andrew Cagney
2003-11-07 17:12 ` Kevin Buettner
2003-11-07 16:25 ` Kevin Buettner
2003-11-07 20:45 ` Andrew Cagney
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=1031023161129.ZM13883@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@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