From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ralph Escherich <esche@mobilesmartsinc.com>
Cc: cgen@sources.redhat.com
Subject: Re: binutils porting to new CPU
Date: Wed, 29 Oct 2003 02:48:00 -0000 [thread overview]
Message-ID: <20031029024802.GA9756@redhat.com> (raw)
In-Reply-To: <200310281821.24902.esche@mobilesmartsinc.com>
Hi -
> [...]
> My research on the web shows, that for a complete port of the binutils
> to a new cpu the follwing parts have to be modified/created:
> [...]
> include/opcodes/FOO.h - Port specific ISA encoding
> opcodes/FOO-dis.c - Port specific disassembler routines
> opcodes/FOO-opc.c - Port specific ISA encoding
These are the only files generated by cgen for binutils, but you'll
notice that these are the primary ones that contain the most complex
aspects for supporting target processor.
The others need to be built by hand. Of these, only the
bfd/{*}-FOO.c file has given me particular headaches, having to
represent object file relocations in a clunky way. (This part
motivated Red Hat to build a reusable generic relocation engine
for a particularly peculiar & reconfigurable target. This code
has not been made public though AFAIK.)
- FChE
next prev parent reply other threads:[~2003-10-29 2:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 2:20 Ralph Escherich
2003-10-29 2:48 ` Frank Ch. Eigler [this message]
2003-10-29 16:37 ` Ralph Escherich
2003-10-29 16:50 ` Frank Ch. Eigler
2003-10-30 0:29 ` Ralph Escherich
2003-10-30 1:53 ` Ben Elliston
2003-10-30 5:46 ` Ralph Escherich
2003-10-30 6:43 ` Ben Elliston
2003-10-30 16:47 ` Ralph Escherich
2003-10-31 4:25 ` Ben Elliston
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=20031029024802.GA9756@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=esche@mobilesmartsinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).