public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Doug Evans <dje@sebabeach.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	  Joseph A <joseph.altmaier@gmail.com>,
	 cgen@sourceware.org
Subject: Re: how can one achieve pipelined operation?
Date: Thu, 02 Jul 2009 12:09:00 -0000	[thread overview]
Message-ID: <4A4CA673.4060708@gmail.com> (raw)
In-Reply-To: <4A4C23E6.60401@sebabeach.org>

Doug Evans wrote:
> Frank Ch. Eigler wrote:
>> Hi -
>>
>>  
>>> I have been working on a port for a while now, and I think everything is
>>> working except the pipeline.  I have tried changing the values of
>>> issue and
>>> done in the functional unit description and I have added a pipeline
>>> statement to define-model.  What do I need to do to achieve pipelined
>>> operation and/or is there an existing example?
>>>     
>>
>> An exposed pipeline is reasonably easily modelled with deferred write
>> queues in a sid-based simulator; see the mep port.
>>
>>   
> 
> Thanks.  The semantics for each instruction are generated from cgen,
> but  the pipeline (i.e. instruction fetch, execute, retire) is handcrafted.
> [Right?]
> 
> Joseph: I think that's the way to go for right now.
> 

  I'm kinda new to cgen and was planning to try soemthing similar.  My first
thought was that I should actually try and explicitly model the different
stages of the pipeline as separate units in my model, and actually pass
instruction operands as outputs from one to the next as inputs, along with a
few control signals like 'stall' and 'ready', with the u-exec unit at the end
of the chain.  Wouldn't that work?

    cheers,
      DaveK

  reply	other threads:[~2009-07-02 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 20:54 Joseph A
2009-07-01 10:50 ` Frank Ch. Eigler
2009-07-02  3:05   ` Doug Evans
2009-07-02 12:09     ` Dave Korn [this message]
2009-07-02 12:29     ` Frank Ch. Eigler
2009-07-02 16:45       ` Joseph A
2009-07-12  2:27         ` Frank Ch. Eigler
2009-07-30 20:12           ` Joseph A
2009-07-30 20:19             ` Frank Ch. Eigler

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=4A4CA673.4060708@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=cgen@sourceware.org \
    --cc=dje@sebabeach.org \
    --cc=fche@redhat.com \
    --cc=joseph.altmaier@gmail.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).