From: Andrew Cagney <cagney@gnu.org>
To: jbeniston@compxs.com
Cc: gdb@sources.redhat.com
Subject: Re: Customizing remote-sim.c on a multi-arch target
Date: Wed, 31 Mar 2004 17:15:00 -0000 [thread overview]
Message-ID: <406AEA67.1060704@gnu.org> (raw)
In-Reply-To: <000601c41701$2e2cca70$09bda8c0@Kindrogan>
> Hi,
>
> I'm trying to customize remote-sim.c on a multi-arch target, what I'd
> look to do is be able to define TARGET_REDEFINE_DEFAULT_OPS so I can
> install hooks to support h/w watchpoints and async execution in my
> simulator. Where should this macro be defined?
Rather than define these macros, what about implementing a new target
(inferior) vector that meets your needs? This is what
> Is this not compatible
> with the multi-arch approach (I notice config/cpu/tx-cpu.h is not
> included for multi-arch builds).
The tm-cpu.h files are obsolete. Instead things are implemented using
an architecture (gdbarch) and target (inferior) vector.
You may also be interested in this:
http://sources.redhat.com/gdb/papers/multi-arch/real-multi-arch/
Andrew
next prev parent reply other threads:[~2004-03-31 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 15:31 Jon Beniston
2004-03-31 17:15 ` Andrew Cagney [this message]
[not found] <406AF7CE.1080902@gnu.org>
2004-04-01 8:59 ` Jon Beniston
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=406AEA67.1060704@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jbeniston@compxs.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