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

Thanks for the help. GCC and friends is a much larger universe
than I expected. 
 
My need is to just assemble, load, and create an S-file for
a PROM burner.
 
There is no need to use the GCC compiler or any higher level
language. 
 
Is CGEN overkill for what I am trying to do?
 
The Z8000 is sort of close to the MECA-43.  Basically all 16 bit
instructions and both 16 and 32 bit data.
 
Looking at the z8kgen.c file and the m32r files made by CGEN
for the m32r there is almost no relation.
 
Looked through the gas opcode documentation. Tried to use 
"makinfo --html" to make the *.texi files readable. But, can't
find the root of the tree of files. Everything fails because
something or another is not defined. Only a few files made any
output. (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.)
 
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.
 
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.
I expect that it should be in the binutils package, but I can't
find it. 
 
Thanks,
Bob Lindley
 
 

             reply	other threads:[~2006-04-04 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 17:34 Lindley, Robert A [this message]
2006-04-04 23:35 ` 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=80890BBB6B38E0419197E69BAE0C989E096DB1@XCH-SW-4V2.sw.nos.boeing.com \
    --to=robert.a.lindley@boeing.com \
    --cc=cgen@sourceware.org \
    --cc=fche@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).