public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Dave Brolley <brolley@redhat.com>
Cc: cgen@sources.redhat.com, gdb-patches@sources.redhat.com,
		sid@sources.redhat.com
Subject: Re: [patch][rfc] sh64: Add Pipeline Modelling and SID Support
Date: Tue, 22 Aug 2006 18:34:00 -0000	[thread overview]
Message-ID: <1156271664.9019.13.camel@localhost.localdomain> (raw)
In-Reply-To: <44EB4A91.6020301@redhat.com>

On Tue, 2006-08-22 at 14:18 -0400, Dave Brolley wrote:
> I would like to commit this patch which does the following for the sh64 
> target:
> 
> 1) Add support for generating a SID simulator.
> 2) Add pipeline modelling for all sh machines (currently used only by SID).
> 3) Adds support for some previously unsupported insns (both SID and 
> sim/sh64).
> 
> I will submit the changes needed for sim/sh64 and sid separately. The 
> sim/sh simulator is currently not generated by CGEN.
> 
> NOTES:
> o This is a patch against the existing sh.cpu, sh64-compact.cpu and 
> sh64-media.cpu in the cgen/cpu directory and which are currently used to 
> generate the sh64 simulator in sim/sh64. .cpu files also exist in the  
> cpu directory, but they appear to be out of date compared to the ones in 
> cgen/cpu. Any clarification regarding which files are being actively 
> maintained would be much appreciated!
> 
> o The new files sh-sid.cpu and sh-sim.cpu provide pmacros for handling 
> the differences between generating sid and sim.
> 
> Comments, concerns and, ultimately, approval to commit please!

Hmmm, sh sim doesn't currently seem to have a maintainer.

Would you like the job?   ;-)


  reply	other threads:[~2006-08-22 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 18:21 Dave Brolley
2006-08-22 18:34 ` Michael Snyder [this message]
2006-10-18 18:08 ` 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=1156271664.9019.13.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=brolley@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=sid@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).