From: "Leung, Felix" <felix.leung@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] RE: dependency violation table problem
Date: Mon, 07 Apr 2003 17:47:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705425@msgid-missing> (raw)
Hi Jim,
Yes what you mentioned is correct. "mem-writers-fp" is missed on
fr-readers line.
The fix will be like what you said by adding IC:mem-writers to the
RAW DV tables.
Both you mentioned will be fixed in the next revision of SDM.
Let me know if you find any other doc errors.
Thanks.
- Felix
-----Original Message-----
From: Jim Wilson <wilson@tuliptree.org>
To: linux-ia64@linuxia64.org
Date: 06 Apr 2003 11:49:09 -0400
Subject: [Linux-ia64] dependency violation table problem
Gas fails for this simple testcase.
.auto
ldfs f8 = [r32]
stfd [r33] = f8
It should insert a stop bit between the load and store, but does not.
This appears to be a bug in the Intel dependency violation (DV) tables.
In the Intel Itanium Architecture Software Developer's Manual (IIASDM),
vol 3, revision 2.1, page 342, table 5-2, says that there is a RAW DV
for a FR% register if fr-writers is followed by fr-readers.
fr-readers is defined on page 352, table 5-5. It includes arith
operations (e.g. add), non-arith operations (e.g. and), and a few other
things, but it does not include stf. This looks like a bug in the Intel
documentation.
I believe this should be fixed by adding IC:mem-writers-fp to
fr-readers. This makes gas work as expected.
As long as I'm reporting documentation problems, there is another less
important one I've noticed. In the X unit instruction encodings, IIASDM
vol 3 rev 2.1 page 332 table 4-73, it mentions nop.m and hint.m. These
should be nop.x and hint.x.
I'm off on a 4000 km international move, so I will be offline for a week
or two.
Jim
reply other threads:[~2003-04-07 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105590723705425@msgid-missing \
--to=felix.leung@intel.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