From: Jim Wilson <wilson@specifixinc.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] new ".serialize" gas directive
Date: Wed, 16 Jun 2004 21:57:00 +0000 [thread overview]
Message-ID: <1087423020.1178.36.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <16537.51724.854691.934006@napali.hpl.hp.com>
On Tue, 2004-06-15 at 18:54, Chris Wedgwood wrote:
> I was just looking over the nested fault handler this thread came to
> mind.
> There is exactly that situation with '.pred.rel "mutex", p6, p7' where
> gas should be able to infer this from the 'cmp.eq p6,p7 = 5,r17'
> preceding this and there are no intermediate labels.
I assume you are talking about the first one in arch/ia64/kernel/ivt.c.
Current gas seems to get this right without the .pred.rel.
I see that the LOAD_PHYSICAL macro expansion includes a tag, which is
kind of like a label. Perhaps there was a problem with tags in earlier
gas versions, or perhaps earlier kernel versions used an actual label
instead of a tag here. Use of a label here may have been necessary
before the assembler had tag support for instance, in which case the
.pred.rel would have been necessary.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-06-16 21:57 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
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 [this message]
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=1087423020.1178.36.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