From: Petr Ledvina <ledvinap@n.cz>
To: "D.Venkatasubramanian, Noida" <dvenkat@noida.hcltech.com>
Cc: <gnuh8@gnuh8.org.uk>, <gdb@sources.redhat.com>
Subject: Re: Adding MAC registers on H8300 Simulator [H8S/2600]
Date: Thu, 20 Feb 2003 16:18:00 -0000 [thread overview]
Message-ID: <Pine.OSF.4.33.0302201705501.9427-100000@eryx1.zcu.cz> (raw)
In-Reply-To: <E04CF3F88ACBD5119EFE00508BBB212107B229E5@exch-01.noida.hcltech.com>
> As the H8S/2600 CPU has MAC registers, specifically
> MACH and MACL, I added them to the H8300 Simulator. How
> do I make GDB recognize these registers, more
> specifically, what are the files that need to be
> modified?
in target definition, NUM_REGS specifies how many registers gdb uses.
REGISTER_NAME return name of given register.
This vector already contains special registers (cycles, inst, .. ), so it
should be possible to add new registers.
gdbstub needs to only know register index mapping, so adding new registers
to end of this list should be compatible.
Also check cvs log, someone (Andrew Volkov?) added exr register recently
to simulator, so he could know better.
> Also, how do I make these registers conditionally
> displayed on GDB when the CPU is H8S/2600.
IIRC gdb knows only h8s target, so this could be quite difficult.
> Any pointers will be highly appreciated. ;-)
Expanding register vector should work fine, but gdb maintainers opinion
may be different ...
Petr Ledvina
ledvinap@n.cz
next prev parent reply other threads:[~2003-02-20 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 15:35 D.Venkatasubramanian, Noida
2003-02-20 16:18 ` Petr Ledvina [this message]
2003-03-12 21:24 ` Michael Snyder
2003-02-20 18:28 Andrew Volkov
2003-02-22 8:51 D.Venkatasubramanian, Noida
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=Pine.OSF.4.33.0302201705501.9427-100000@eryx1.zcu.cz \
--to=ledvinap@n.cz \
--cc=dvenkat@noida.hcltech.com \
--cc=gdb@sources.redhat.com \
--cc=gnuh8@gnuh8.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).