From: Randolph Chung <randolph@tausq.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/commit] function descriptor handling for push_dummy_call
Date: Mon, 07 Jun 2004 04:31:00 -0000 [thread overview]
Message-ID: <20040607043143.GF601@tausq.org> (raw)
In-Reply-To: <3405-Mon07Jun2004072253+0300-eliz@gnu.org>
> Please say @code{struct value}. Since these are C identifiers, they
> should appear in an appropriate typeface in the printed version.
committed, thanks.
randolph
2004-06-06 Randolph Chung <tausq@debian.org>
* gdb.texinfo (push_dummy_call): Use @code{struct value}.
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.204
diff -u -p -r1.204 gdbint.texinfo
--- gdbint.texinfo 7 Jun 2004 02:12:59 -0000 1.204
+++ gdbint.texinfo 7 Jun 2004 04:31:01 -0000
@@ -3643,7 +3643,7 @@ the inferior function onto the stack. I
@var{nargs}, the code should push @var{struct_addr} (when
@var{struct_return}), and the return address (@var{bp_addr}).
-@var{function} is a pointer to a struct value; on architectures that use
+@var{function} is a pointer to a @code{struct value}; on architectures that use
function descriptors, this contains the function descriptor value.
Returns the updated top-of-stack pointer.
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
prev parent reply other threads:[~2004-06-07 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 6:10 [patch/rfa] " Randolph Chung
2004-06-04 18:44 ` Andrew Cagney
2004-06-05 10:17 ` Eli Zaretskii
2004-06-05 13:36 ` Andrew Cagney
2004-06-05 15:58 ` Eli Zaretskii
2004-06-05 16:23 ` Randolph Chung
2004-06-05 21:12 ` Eli Zaretskii
2004-06-07 2:15 ` [patch/commit] " Randolph Chung
2004-06-07 4:25 ` Eli Zaretskii
2004-06-07 4:31 ` Randolph Chung [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=20040607043143.GF601@tausq.org \
--to=randolph@tausq.org \
--cc=eliz@gnu.org \
--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