From: "Mattox, Dave" <DMattox@UNITECH.COM>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Multimedia Instructions
Date: Fri, 20 Oct 2000 22:16:19 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205602@msgid-missing> (raw)
Couple questions for you all if you don't mind:
1. Is there a mailing list for information on just IA-64? A majority of my
issues deal with the architecture exclusively and I don't want to pollute
this mailing list. If anyone knows of one I would appreciate a link.
2. Does anyone know if the 10 clock cycle penalty for a multimedia
instruction result used in a different instruction type is just a quirk of
the Itanium Chip or will this most likely be carried into future IA-64
Chipsets? If this penalty is likely to disappear in future versions, I don't
mind coding it for a hit now.
The penalty I am talking about is a code segment such as:
mux1 r36 = r37, @rev;; // mm instruction
add r38 = 5, r36 // 10 clock penalty for using result in a
different instruction type
It's interesting how the following is actually faster:
mux1 r36 = r37, @rev;;
nop;;
nop;;
nop;;
nop;;
add r38 = 5, r36
Thanks,
Dave Mattox
next reply other threads:[~2000-10-20 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-20 22:16 Mattox, Dave [this message]
2000-10-20 23:25 ` [Linux-ia64] Multimedia Instructions Dan Pop
2000-10-20 23:59 ` Mattox, Dave
2000-10-23 14:47 ` Saxena, Sunil
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=marc-linux-ia64-105590678205602@msgid-missing \
--to=dmattox@unitech.com \
--cc=linux-ia64@vger.kernel.org \
/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