From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen@sources.redhat.com
Subject: exposed pipeline patch (long!)
Date: Thu, 09 Jan 2003 07:24:00 -0000 [thread overview]
Message-ID: <15901.9079.191603.469002@casey.transmeta.com> (raw)
In-Reply-To: <m3vg0zm29f.fsf@scooby.brisbane.redhat.com>
Handling exposed pipelines can get really messy
when one takes bypass networks into account.
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.
If they're implementation related (e.g. related to the depth of
the pipeline), then I think rtl isn't the way to go.
[I suppose an ISA could specify the depth of the pipeline
but that wouldn't be the norm.]
One way to go would be to specify the hazards independently of the rtl.
next prev parent reply other threads:[~2003-01-09 7:24 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 [this message]
2003-01-09 17:17 ` Frank Ch. Eigler
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=15901.9079.191603.469002@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=bje@redhat.com \
--cc=cgen@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).