From: David Carney <dfcarney@net-itech.com>
To: cgen@sources.redhat.com
Subject: opcodes port
Date: Tue, 31 Dec 2002 13:11:00 -0000 [thread overview]
Message-ID: <200212311611.15926.dfcarney@net-itech.com> (raw)
I'm following the instructions in section 5.5 of the cgen manual regarding an
opcodes port and have a couple questions:
i) step 7. says to repeat steps 4, 5, and 6 until the output looks reasonable.
What is the definition of "reasonable" output?
ii) how do I get Guile to actually output and write the generated files to
disk? I.e. when I run (cgen-desc.h) I get a nice header file listing, but
it's not saved anywhere. Should I just cut-and-paste, or is there some
Guile/scheme command to redirect output? I'm assuming that the makefiles in
binutils are responsible for running cgen and generating the appropriate
files, but I'm unclear as to how to configure them to point to the directory
in which I have cgen installed and, furthermore, how to actually have the
makefile autogenerate the files for my new architecture...
iii) the opcode-port directions say nothing about how to configure binutils.
Simply going to a "clean" opcodes directory and editing Makefile.am is
clearly not enough to allow you to run a successful 'make dep' (as no
makefile actually exists until 'configure' is run from the parent directory).
Doesn't the configure script need to be modified also? What about
Makefile.in?
iv) and because my understanding of binutils is rather vague... what will
running make dep in /opcodes actually produce for me? what do I need to do
with the resultant files?
Overall, I'm getting a handle on how to write a .cpu file, but I'm still
virtually clueless when it comes to using it in conjunction with binutils to
produce an assembler...
Dave Carney
next reply other threads:[~2002-12-31 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 13:11 David Carney [this message]
2003-01-02 1:43 ` 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=200212311611.15926.dfcarney@net-itech.com \
--to=dfcarney@net-itech.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).