From: Mark Kettenis <kettenis@chello.nl>
To: eliz@is.elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add machine type to gdbarch_register_osbi
Date: Sun, 22 Dec 2002 11:45:00 -0000 [thread overview]
Message-ID: <200212221825.gBMIP9hb010989@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1021222081545.28392H-100000@is> (message from Eli Zaretskii on Sun, 22 Dec 2002 08:16:20 +0200 (IST))
Date: Sun, 22 Dec 2002 08:16:20 +0200 (IST)
From: Eli Zaretskii <eliz@is.elta.co.il>
On Sat, 21 Dec 2002, Mark Kettenis wrote:
> Last week brought us two new gdbarch_init_osabi calls, so below is
> what I actually checked in.
Is this function documented in gdbint.texinfo? If so, the docs needs to
be updated as well.
How about the attached patch?
Mark
Index: doc/ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* gdbint.texinfo (Target Architecture Definition): Update
description of gdbarch_register_osabi.
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.110
diff -u -p -r1.110 gdbint.texinfo
--- doc/gdbint.texinfo 11 Dec 2002 02:26:38 -0000 1.110
+++ doc/gdbint.texinfo 22 Dec 2002 18:24:45 -0000
@@ -2424,9 +2424,12 @@ Here are the functions that make up the
Return the name of the OS ABI corresponding to @var{osabi}.
@end deftypefun
-@deftypefun void gdbarch_register_osabi (enum bfd_architecture @var{arch}, enum gdb_osabi @var{osabi}, void (*@var{init_osabi})(struct gdbarch_info @var{info}, struct gdbarch *@var{gdbarch}))
+@deftypefun void gdbarch_register_osabi (enum bfd_architecture @var{arch}, unsigned long @var{machine}, enum gdb_osabi @var{osabi}, void (*@var{init_osabi})(struct gdbarch_info @var{info}, struct gdbarch *@var{gdbarch}))
Register the OS ABI handler specified by @var{init_osabi} for the
-architecture/OS ABI pair specified by @var{arch} and @var{osabi}.
+architecture, machine type and OS ABI specified by @var{arch},
+@var{machine} and @var{osabi}. In most cases, a value of zero for the
+machine type, which implies the architecture's default machine type,
+will suffice.
@end deftypefun
@deftypefun void gdbarch_register_osabi_sniffer (enum bfd_architecture @var{arch}, enum bfd_flavour @var{flavour}, enum gdb_osabi (*@var{sniffer})(bfd *@var{abfd}))
next prev parent reply other threads:[~2002-12-22 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 13:11 Mark Kettenis
2002-12-22 3:03 ` Eli Zaretskii
2002-12-22 11:45 ` Mark Kettenis [this message]
2002-12-22 15:27 ` Eli Zaretskii
2002-12-23 11:58 ` Mark Kettenis
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 10:32 Mark Kettenis
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=200212221825.gBMIP9hb010989@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--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