From: David Carney <dfcarney@net-itech.com>
To: cgen@sources.redhat.com
Cc: bje@redhat.com
Subject: Re: cgen fundamentals
Date: Thu, 19 Dec 2002 11:34:00 -0000 [thread overview]
Message-ID: <200212191433.48565.dfcarney@net-itech.com> (raw)
In-Reply-To: <m33couajly.fsf@scooby.brisbane.redhat.com>
> Hi David. Welcome.
Thanks.
> CGEN is a framework, in which CGEN applications run. There are a
> handful of these now: an opcodes table generator, a simulator kernel
> generator, and so on. If you just want to port binutils, you need
> only concern yourself with generating the opcodes/* files. The GNU
> binutils "opcodes" directory has Makefile fragments for other ports
> (like fr30) that can be duplicated almost verbatim. These Makefile
> fragment are responsible for running CGEN for you and depositing the
> output files in the opcodes/ source directory. I would suggest you
> focus on writing your CPU description first and then work out how to
> run it from opcodes/Makefile.
>
> Please feel free to ask more questions on this otherwise quiet list!
Oh, I will. Don't worry... :)
So, basically, I define my own .cpu file and add a new target to the
binutils/opcodes Makefile (that'll use cgen in conjunction with my .cpu
file), correct? After I get cgen to properly generate files for
binutils/opcodes, I'll need to write my own cpu-???.* and elf32-???.* files
for the binutils/bfd, right?
What else will I need to do to get an assembler up and running?
Thanks,
Dave
next prev parent reply other threads:[~2002-12-19 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 15:23 David Carney
2002-12-18 17:31 ` Ben Elliston
2002-12-19 11:34 ` David Carney [this message]
2002-12-19 14:12 ` Ben Elliston
2002-12-19 4:51 ` Frank Ch. Eigler
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=200212191433.48565.dfcarney@net-itech.com \
--to=dfcarney@net-itech.com \
--cc=bje@redhat.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).