Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [rfc] Replace macros by gdbarch functions in gdbint manual
Date: Wed, 27 Jun 2007 18:35:00 -0000	[thread overview]
Message-ID: <u1wfxntc4.fsf@gnu.org> (raw)
In-Reply-To: <4681382D.1070708@de.ibm.com> (message from Markus Deuling on 	Tue, 26 Jun 2007 18:00:45 +0200)

> Date: Tue, 26 Jun 2007 18:00:45 +0200
> From: Markus Deuling <deuling@de.ibm.com>
> CC: gdb-patches@sourceware.org, uweigand@de.ibm.com
> 
> again thank you very much for your time.

And thank _you_ for working on this in the first place.

> Is this ok to commit?

Yes, but:

> -and to reflect that in the @code{REGISTER_NAME} and related macros.
> +nd to reflect that in the @code{gdbarch_register_name} and related functions.
   ^^
"and"

> +address of the instruction.  gdbarch_addr_bits_remove would then for example

Please gibe gdbarch_addr_bits_remove a @code markup.

> +@findex gdbarch_ps_regnum
> +If defined, this function returns is the number of the processor status
                                     ^^
The "is" part should be removed.

> +the inferior function onto the stack.  In addition to pushing @var{nargs}, the
> +code should push @var{struct_addr} (when @var{struct_return}), and the return
                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
It looks like something is missing in the parens.  The old text also
had this problem; can someone suggest or guess what was meant here?

Other than that, the patch can go in.


  reply	other threads:[~2007-06-27 18:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 10:19 Markus Deuling
2007-06-20 18:32 ` Eli Zaretskii
2007-06-22  7:10   ` Markus Deuling
2007-06-23  8:05     ` Eli Zaretskii
2007-06-23 12:29       ` Daniel Jacobowitz
2007-06-26 17:36       ` Markus Deuling
2007-06-27 18:35         ` Eli Zaretskii [this message]
2007-06-28  3:10           ` Daniel Jacobowitz
2007-06-28  4:53             ` Eli Zaretskii
2007-06-28 10:46               ` Markus Deuling
2007-06-29 18:33                 ` Eli Zaretskii
2007-06-28 21:01               ` Jim Blandy
2007-06-29 17:46                 ` Eli Zaretskii
     [not found] <4688B47B.1000301@de.ibm.com>
2007-07-03 12:23 ` Ulrich Weigand

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=u1wfxntc4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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