From: Jim Blandy <jimb@redhat.com>
To: "Xinan Tang" <xinan@tidalnetworks.net>
Cc: <gdb@sources.redhat.com>
Subject: Re: "Info reg doesn't work"
Date: Fri, 18 Jun 2004 04:07:00 -0000 [thread overview]
Message-ID: <vt2brjhv794.fsf@zenia.home> (raw)
In-Reply-To: <KAEHILJLFHMPJPLKAFBHOEDECBAA.xinan@tidalnetworks.net>
"Xinan Tang" <xinan@tidalnetworks.net> writes:
> Should I go into function _initialize_FOO_tdep() to modify the places
> where bfd_arch_arm is used? I haven't done that yet since our target is
> similar to arm.
Well, you're going to need to choose your own bfd_arch_* value, and
use that in the upstream toolchain. Or if your processor is a variant
on the ARM, then you'll need to invent your own bfd_mach_arm_* value.
Ask on binutils@sources.redhat.com about allocating a bfd_arch or
bfd_mach value for your own use. I haven't done this before.
next prev parent reply other threads:[~2004-06-18 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 23:49 Xinan Tang
2004-06-15 22:42 ` Jim Blandy
2004-06-16 0:04 ` Xinan Tang
2004-06-18 4:07 ` Jim Blandy [this message]
2004-06-23 2:38 ` Xinan Tang
2004-06-23 5:05 ` Jim Blandy
[not found] <KAEHILJLFHMPJPLKAFBHAEDFCBAA.xinan@tidalnetworks.net>
2004-06-16 1:53 ` Jim Blandy
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=vt2brjhv794.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=xinan@tidalnetworks.net \
/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).