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, 20 Jun 2007 18:32:00 -0000 [thread overview]
Message-ID: <u7ipyqxxz.fsf@gnu.org> (raw)
In-Reply-To: <4678FEBE.7040209@de.ibm.com> (message from Markus Deuling on Wed, 20 Jun 2007 12:17:34 +0200)
> Date: Wed, 20 Jun 2007 12:17:34 +0200
> From: Markus Deuling <deuling@de.ibm.com>
> CC: Ulrich Weigand <uweigand@de.ibm.com>
>
> this patch replaces the macros that have been replaced in gdbarch.sh in GDB's manuals.
Thanks.
> Is this ok to commit?
Yes, after you take care of the following gotchas:
> -@deftypefn {Target Macro} CORE_ADDR POINTER_TO_ADDRESS (struct type *@var{type}, char *@var{buf})
> +@deftypefn {Target Macro} CORE_ADDR gdbarch_pointer_to_address (struct gdbarch *@var{current_gdbarch}, struct type *@var{type}, char *@var{buf})
You've replaced a macro with a function, so "Target Macro" is no
longer appropriate. (There are many more instances like this one.)
> -@anchor{BREAKPOINT_FROM_PC} Use the program counter to determine the
> +@item gdbarch_breakpoint_from_pc (@var{current_gdbarch}, @var{pcptr}, @var{lenptr})
> +@findex gdbarch_breakpoint_from_pc
> +@anchor{gdbarch_breakpoint_from_pc} Use the program counter to determine the
Presumably, some @xref uses this @anchor, and that @xref will need to
be changed as well, but I don't see any such changes in the patch.
What am I missing?
> -@item DECR_PC_AFTER_BREAK
> -@findex DECR_PC_AFTER_BREAK
> -Define this to be the amount by which to decrement the PC after the
> +@item gdbarch_decr_pc_after_break (@var{current_gdbarch})
> +@findex gdbarch_decr_pc_after_break
> +Set this to the amount by which to decrement the PC after the
A macro can be defined to a constant value, but how can one ``set'' a
function to do the same? (Again, there are several similar problems
with ``setting'' a function.
> --- src/gdb/doc/gdb.texinfo 2007-06-19 05:22:05.000000000 +0200
> +++ dev/gdb/doc/gdb.texinfo 2007-06-20 10:49:17.000000000 +0200
> @@ -22763,8 +22763,8 @@
> Each byte of register data is described by two hex digits. The bytes
> with the register are transmitted in target byte order. The size of
> each register and their position within the @samp{g} packet are
> -determined by the @value{GDBN} internal macros
> -@code{DEPRECATED_REGISTER_RAW_SIZE} and @code{REGISTER_NAME} macros. The
> +determined by the @value{GDBN} internal gdbarch functions
> +@code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}. The
DEPRECATED_REGISTER_RAW_SIZE is not a function, is it?
Thanks again for working on this.
next prev parent reply other threads:[~2007-06-20 18:32 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 [this message]
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
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=u7ipyqxxz.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