From: Elena Zannoni <ezannoni@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: ezannoni@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Multiarch tm_print_insn
Date: Tue, 04 Sep 2001 21:00:00 -0000 [thread overview]
Message-ID: <15253.42307.875233.300520@krustylu.cygnus.com> (raw)
In-Reply-To: <9003-Thu23Aug2001085323+0300-eliz@is.elta.co.il>
Eli Zaretskii writes:
> > From: Elena Zannoni <ezannoni@cygnus.com>
> > Date: Wed, 22 Aug 2001 18:19:14 -0400
> >
> > > > This patch multiarches tm_print_insn.
> > > > I changed all the direct callers to (*tm_print_insn), to use
> > > > the multiarch macro TARGET_PRINT_INSN.
> > >
> > > Should this macro be documented in gdbint.texinfo?
> >
> > In which section should it go?
>
> The section "Target conditionals" sounds about right.
How about this?
[Note: I don't know how to reference correctly the 'opcodes' library.]
Elena
2001-09-04 Elena Zannoni <ezannoni@redhat.com>
* gdbint.texinfo (Target Architecture Definition): Add
explanation of TARGET_PRINT_INSN macro.
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.35
diff -u -p -r1.35 gdbint.texinfo
--- gdbint.texinfo 2001/08/15 14:47:53 1.35
+++ gdbint.texinfo 2001/09/05 03:59:40
@@ -3566,6 +3566,17 @@ If non-zero, the target has support for
watchpoints. @xref{Algorithms, watchpoints}, for more details and
other related macros.
+@item TARGET_PRINT_INSN (@var{addr}, @var{info})
+@findex TARGET_PRINT_INSN
+This is the function used by @value{GDBN} to print an assembly
+instruction. It prints the instruction at address @var{addr} in
+debugged memory abd returns the length of the instruction, in bytes. If
+a target doesn't define its own printing routine, it defaults to an
+accessor function for the global pointer @var{tm_print_insn}. This
+usually points to a function in the @code{opcodes} library
+(@xref{,,opcodes}). @var{info} is a structure defined in @code{opcodes}
+used to pass information to the instruction decoding routine.
+
@item USE_STRUCT_CONVENTION (@var{gcc_p}, @var{type})
@findex USE_STRUCT_CONVENTION
If defined, this must be an expression that is nonzero if a value of the
next prev parent reply other threads:[~2001-09-04 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 16:26 Elena Zannoni
2001-08-21 17:33 ` Andrew Cagney
2001-09-05 17:07 ` Elena Zannoni
[not found] ` <3405-Wed22Aug2001084554+0300-eliz@is.elta.co.il>
[not found] ` <15236.12258.330506.371048@krustylu.cygnus.com>
[not found] ` <9003-Thu23Aug2001085323+0300-eliz@is.elta.co.il>
2001-09-04 21:00 ` Elena Zannoni [this message]
2001-09-05 3:12 ` Eli Zaretskii
2001-09-05 11:58 ` Elena Zannoni
2001-09-06 0:47 ` Eli Zaretskii
2001-09-06 5:02 ` Elena Zannoni
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=15253.42307.875233.300520@krustylu.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=eliz@is.elta.co.il \
--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