public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Lindley, Robert A" <robert.a.lindley@boeing.com>
Cc: cgen@sourceware.org
Subject: Re: I mainly need an as and ld port
Date: Tue, 04 Apr 2006 23:35:00 -0000	[thread overview]
Message-ID: <20060404233551.GB16498@redhat.com> (raw)
In-Reply-To: <80890BBB6B38E0419197E69BAE0C989E096DB1@XCH-SW-4V2.sw.nos.boeing.com>

Hi -

> [...]  Is CGEN overkill for what I am trying to do?

Not really, but recall that even CGEN handles only a part of the
binutils port.  There is stuff to hand-write with or without CGEN,
and of course more without it.

> The Z8000 is sort of close to the MECA-43.  Basically all 16 bit
> instructions and both 16 and 32 bit data.

The more regular, RISC-like the instruction set, the better fit
it is for CGEN.

> [...] I have no clue how to run Emacs and the info document reader
> thing doesn't know anything about the files that I want to look at.)

The "make info" in build directories like gas/, bfd/, etc. can help,
and some even have a "make html" target in their doc/ subdirs.  If
it's too much hassle to figure it out, of course the .texi files are
readable ASCII.


> I can't find out how to make a file like z8kgen.c. All the things
> are encoded with codes that I can't find any description of.

z8kgen.c is not related to cgen, except perhaps as a motivation.
There are several other generator type tools in the whole toolchain
(for another, see igen in the gdb simulators).  CGEN was meant to
unify and generalize them.

> Your suggestion of hand-written gas/bfd/ld/simulator code seems
> the way to go. Hours of searching has produced no results for
> information on the exact files to be made, the exact format of
> each files,  how to update the make files for automake, etc. etc.

There is no substitute for a certain amount of self-education to gain
familiarity with the configury system in general, and the specific
build procedure for a similar existing target.

My simple recipe is to duplicate an existing target by a mass copy &
rename.  Pick a base target for replication like "iq2000" or "ip2k",
which are strings unlikely to occur elsewhere.

- FChE

      reply	other threads:[~2006-04-04 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 17:34 Lindley, Robert A
2006-04-04 23:35 ` Frank Ch. Eigler [this message]

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=20060404233551.GB16498@redhat.com \
    --to=fche@redhat.com \
    --cc=cgen@sourceware.org \
    --cc=robert.a.lindley@boeing.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).