public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Lindley, Robert A" <robert.a.lindley@boeing.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <cgen@sourceware.org>
Subject: RE: How do I run CGEN?
Date: Fri, 17 Mar 2006 14:28:00 -0000	[thread overview]
Message-ID: <80890BBB6B38E0419197E69BAE0C989E096D82@XCH-SW-4V2.sw.nos.boeing.com> (raw)
In-Reply-To: <20060316153045.GA30997@redhat.com>

Thanks,
 
Is there a preliminary, draft, or working copy of Chapter 2?
Is someone working on it?
Perhaps if I made notes on my adventure through this maze 
it would be of some help?
 
To someone who knows the inner workings of gas and ld, cgen
may seems easy and intuitive. However, I am starting this journey 
from square zero. As such, I need a high level overview of the the
tasks that must be accomplished and the order that they must be done.
 
I am going to re-read the available, and very detailed, documentation.
I think that I need to know more about how gas and ld work to get
a better idea about how all of this fits together.
 
Bob Lindley

________________________________

From: Frank Ch. Eigler [mailto:fche@redhat.com]
Sent: Thu 3/16/2006 8:30 AM
To: Lindley, Robert A
Cc: cgen@sourceware.org
Subject: Re: How do I run CGEN?



Hi -

> [...] Can't find anything that gives a top level discussion of how
> to accomplish the series of tasks that define a processor to making
> a new as and ld. [...]  I need to define a unique (MECA-43)
> processor and can't get started.

Despite the documentation, most cgen users tend to run it in batch
mode only.  A new port is typically done by replicating an existing
port with a new name throughout source tree, making that build, then
modifying it to represent the actual target CPU.

An old thread gives an outline of the other (cgen-unassisted) parts of
binutils porting: http://sourceware.org/ml/cgen/2003-q4/msg00014.html

- FChE


  parent reply	other threads:[~2006-03-17 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 22:07 Lindley, Robert A
2006-03-16 15:30 ` Frank Ch. Eigler
2006-03-16 16:42   ` Dave Brolley
2006-03-17 14:28   ` Lindley, Robert A [this message]
2006-03-17 20:00     ` Frank Ch. Eigler
2006-03-17 20:34       ` Dave Brolley

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=80890BBB6B38E0419197E69BAE0C989E096D82@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).