From: Jim Wilson <wilson@specifixinc.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] new ".serialize" gas directive
Date: Thu, 06 May 2004 23:33:36 +0000 [thread overview]
Message-ID: <1083886417.1078.134.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <16537.51724.854691.934006@napali.hpl.hp.com>
On Wed, 2004-05-05 at 22:15, David Mosberger wrote:
> tbit.z p34, p35 = r22, 12 ;;
> (p34) cmp4.eq p6, p7 = 2, r15
> (p35) cmp4.eq p6, p7 = 3, r15 ;;
> (p6) addl r14 = 1, r0
> (p7) mov r14 = r0
This one has complications. If r22 has the NaT bit set, then the result
of the tbit.z is to set both p34 and p35 to zero. Thus p6, p7 are not
set, and it is possible that they both could be true if we have no
information about them, in which case there is a DV here. If we know
that r22 can not have the NaT bit set, then one and only one of p34 or
p35 will be true in which case at most one of p6 or p7 can be true, in
which case there is no DV. So resolving this needs extra information
about NaT bits and/or the previous values of p6/p7. I am not sure if
gas can get this right. It may not have enough info. This may also be
a gcc bug, since this code isn't safe if r22 can have a NaT bit set, and
I seriously doubt that gcc checks for this case.
At the moment, neither gcc nor gas really knows anything about NaT bits.
> * config/tc-ia64.c (dot_serialize): Declare.
> (dot_serialize): New function.
> (md_pseudo_table): Add ".serialize.data" and
> ".serialize.instruction" directives.
The patch looks fine to me. I checked it in.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-05-06 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 5:15 [PATCH] new ".serialize" gas directive David Mosberger
2004-05-06 23:33 ` Jim Wilson [this message]
2004-05-06 23:47 ` David Mosberger
2004-05-07 7:48 ` Jim Wilson
2004-05-10 20:16 ` David Mosberger
2004-05-14 8:43 ` Jim Wilson
2004-05-14 18:30 ` David Mosberger
2004-06-16 1:54 ` Chris Wedgwood
2004-06-16 21:57 ` Jim Wilson
2004-06-16 22:04 ` Chris Wedgwood
2004-06-16 22:42 ` Jim Wilson
2004-06-16 22:56 ` Luck, Tony
2004-06-16 23:01 ` David Mosberger
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=1083886417.1078.134.camel@leaf.tuliptree.org \
--to=wilson@specifixinc.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