From: fche@redhat.com (Frank Ch. Eigler)
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: exposed pipeline patch (long!)
Date: Thu, 09 Jan 2003 17:17:00 -0000 [thread overview]
Message-ID: <o5adiaxmyh.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <15901.9079.191603.469002@casey.transmeta.com>
dje wrote:
> Handling exposed pipelines can get really messy
> when one takes bypass networks into account.
... right, which is why we don't model bypass networks at all in RTL.
> Question: For the ports in question, are the delays ISA related
> or implementation related?
> If they're ISA related then specifying the delays in rtl is appropriate.
> [...]
That's right.
> One way to go would be to specify the hazards independently of the rtl.
Right, and to some extent, the cgen "model" machinery may enable this.
They are orthogonal animals.
- FChE
next prev parent reply other threads:[~2003-01-09 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 3:27 Ben Elliston
2003-01-09 6:41 ` Doug Evans
2003-01-09 17:55 ` Frank Ch. Eigler
2003-01-09 18:36 ` Doug Evans
2003-01-09 19:14 ` Frank Ch. Eigler
2003-01-12 17:05 ` Doug Evans
2003-01-09 19:12 ` graydon hoare
2003-01-12 17:21 ` Doug Evans
2003-01-09 6:55 ` Doug Evans
2003-01-09 7:24 ` Doug Evans
2003-01-09 17:17 ` Frank Ch. Eigler [this message]
2003-01-12 17:54 ` Doug Evans
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=o5adiaxmyh.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).