public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: cgen@sources.redhat.com
Subject: Re: opcodes port
Date: Thu, 02 Jan 2003 01:43:00 -0000	[thread overview]
Message-ID: <m3u1gsz5ql.fsf@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <200212311611.15926.dfcarney@net-itech.com>

Hi David,

>>>>> "David" == David Carney <dfcarney@net-itech.com> writes:

  David> I'm following the instructions in section 5.5 of the cgen
  David> manual regarding an opcodes port and have a couple questions:

  David> i) step 7. says to repeat steps 4, 5, and 6 until the output
  David> looks reasonable.  What is the definition of "reasonable"
  David> output?

This comment made more sense in the early days of CGEN development.  I
would not pay too much attention to it now.  If you are happy with
your .cpu input file, then you should deem that the output "looks
reasonable". ;-)

  David> ii) how do I get Guile to actually output and write the
  David> generated files to disk?  I.e. when I run (cgen-desc.h) I get
  David> a nice header file listing, but it's not saved anywhere.
  David> Should I just cut-and-paste, or is there some Guile/scheme
  David> command to redirect output?  I'm assuming that the makefiles
  David> in binutils are responsible for running cgen and generating
  David> the appropriate files, but I'm unclear as to how to configure
  David> them to point to the directory in which I have cgen installed
  David> and, furthermore, how to actually have the makefile
  David> autogenerate the files for my new architecture...

Just mimic one of the existing ports in opcodes/Makefile.am.  Take
fr30 as an example; search through Makefile.am for all occurrences of
`fr30' and follow in a near-identical fashion.

One that is done, run `automake' in the opcodes source tree.  Then
configure an opcodes build directory:

        $ mkdir build && cd build
        $ /path/to/src/opcodes/configure
        $ make stamp-foo

(where `foo' is your target architecture).

  David> iv) and because my understanding of binutils is rather
  David> vague...  what will running make dep in /opcodes actually
  David> produce for me?  what do I need to do with the resultant
  David> files?

make dep will update the dependencies in Makefile.am, I believe.

  David> Overall, I'm getting a handle on how to write a .cpu file,
  David> but I'm still virtually clueless when it comes to using it in
  David> conjunction with binutils to produce an assembler...

Understandable! :)

Hope this helps,
Ben


      reply	other threads:[~2003-01-02  1:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 13:11 David Carney
2003-01-02  1:43 ` Ben Elliston [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=m3u1gsz5ql.fsf@scooby.brisbane.redhat.com \
    --to=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).