public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: jemarch@gnu.org (Jose E. Marchesi)
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sourceware.org
Subject: Re: Hi there
Date: Thu, 19 Jan 2012 21:01:00 -0000	[thread overview]
Message-ID: <87d3afmmp0.fsf@gnu.org> (raw)
In-Reply-To: <20120119192019.GA4174@redhat.com> (Frank Ch. Eigler's message of	"Thu, 19 Jan 2012 14:20:19 -0500")


    > I am using cgen for the development of a LEON3 simulator, partly funded
    > by my employer.
    
    Neat.  Are you starting from one of the other SPARC models?

Probably yes.  I am currently reading the cgen/cpu/sparc*.cpu RTL files.
It looks like they are not being updated since long ago, and that they
are not being used in binutils.

I copied them into my local git repo (which will be public as soon as I
reach a stage where at least the ISA simulator runs) since I need to do
extensive modifications, such as explicitly supporting a V7 machine for
ERC32 and the models themselves.

    Which simulator framework are you planning to use (gdb/sim vs. sid)?

gdb.  I am still in the stage on getting familiar with the common sim
infrastructure, but it looks like it provides enough flexibility (in
terms of buses, signals, etc) for my purposes.

Besides, my company filed a copyright assignment for gdb, and I have got
a personal one in place as well :)

BTW, do I need to sign separated papers for CGEN?

-- 
Jose E. Marchesi         http://www.jemarch.net
GNU Project              http://www.gnu.org

  reply	other threads:[~2012-01-19 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 19:18 Jose E. Marchesi
2012-01-19 19:20 ` Frank Ch. Eigler
2012-01-19 21:01   ` Jose E. Marchesi [this message]
2012-01-19 21:04     ` Frank Ch. Eigler
2012-01-19 21:30       ` Jose E. Marchesi

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=87d3afmmp0.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --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).