Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc, rfa:doco] gdbarch return value
Date: Fri, 03 Oct 2003 18:14:00 -0000	[thread overview]
Message-ID: <9743-Fri03Oct2003201110+0200-eliz@elta.co.il> (raw)
In-Reply-To: <3F7C630B.1040506@redhat.com> (message from Andrew Cagney on Thu, 02 Oct 2003 13:40:27 -0400)

> Date: Thu, 02 Oct 2003 13:40:27 -0400
> From: Andrew Cagney <ac131313@redhat.com>
> 
> This implements the "return_value" method I proposed earlier this week.
>   It replaces USE_STRUCT_CONVENTION, EXTRACT_RETURN_VALUE, and
> STORE_RETURN_VALUE.  The implementation is fallout from me fixing the
> ppc64 return code and finding that a single "reurn_value" method lead to
> more robust code.

The doco part is okay with me, but I'd suggest to move this paragraph:

  +Given a function with a return-value of type @var{rettype}, return which
  +return-value convention that function would use.

right after these two lines:

  +@item enum return_value_convention gdbarch_return_value (struct gdbarch *@var{gdbarch}, struct type *@var{valtype}, struct regcache *@var{regcache}, const void *@var{inval}, void *@var{outval})
  +@findex gdbarch_return_value

since it describes what the method does, while the rest explains more
about the matter.


  reply	other threads:[~2003-10-03 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02 17:40 Andrew Cagney
2003-10-03 18:14 ` Eli Zaretskii [this message]
2003-10-03 19:38   ` Andrew Cagney
2003-10-20 15:47 ` 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=9743-Fri03Oct2003201110+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --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