From: Ralph Escherich <esche@mobilesmartsinc.com>
To: cgen@sources.redhat.com
Subject: binutils porting to new CPU
Date: Wed, 29 Oct 2003 02:20:00 -0000 [thread overview]
Message-ID: <200310281821.24902.esche@mobilesmartsinc.com> (raw)
Hi,
I wanted to port the gnu gcc and binutils to a new cpu architecture. Searching
on the web revealed, that cgen should be able to generate all necessary
modifications for the binutils portion from a single cpu description file.
Searching through the cgen mailing list, I was able to get cgen running. It
generates appropriate files in the binutils/opcode directory, but nothing
else.
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:
Basically you will need to create these files. (Replace FOO with the
name of your chip):
gas/config/tc-FOO.h - Customisation of generic parts of the
assembler
gas/config/tc-FOO.c - Port specific parts of the assembler
include/{coff|elf}/FOO.h - Port specific header file
include/opcodes/FOO.h - Port specific ISA encoding
opcodes/FOO-dis.c - Port specific disassembler routines
opcodes/FOO-opc.c - Port specific ISA encoding
bfd/{elf32|coff}-FOO.c - Port specific relocation handlers
bfd/cpu-FOO.c - Port specific description of the CPU
ld/scripttempl/FOO.sc - Port specific linker template file
ld/emulparam/FOO.sh - Port specific linker customisation
You will also need to add support for your chip to the various
configuration files:
gas/configure.in
opcodes/configure.in
bfd/configure.in
bfd/config.bfd
bfd/archures.c
bfd/reloc.c
ld/configure.in
ld/configure.tgt
include/dis-asm.h
So my basic questions:
1.) Is cgen supposed to do all the above changes, file generations?
2.) If not all, what does it generate and how can it really be used?
Esche
next reply other threads:[~2003-10-29 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 2:20 Ralph Escherich [this message]
2003-10-29 2:48 ` Frank Ch. Eigler
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=200310281821.24902.esche@mobilesmartsinc.com \
--to=esche@mobilesmartsinc.com \
--cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).