From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.4 remove intermittent warnings from spinlock code
Date: Tue, 16 Mar 2004 07:34:43 +0000 [thread overview]
Message-ID: <16470.44563.416335.867593@napali.hpl.hp.com> (raw)
In-Reply-To: <2465.1079310276@kao2.melbourne.sgi.com>
>>>>> On Mon, 15 Mar 2004 11:24:36 +1100, Keith Owens <kaos@sgi.com> said:
Keith> The spinlock code writes to p14. If gcc reuses p14 in the
Keith> bundles immediately after the spinlock then we get warning
Keith> messages. Append a stop bit to the spinlock code to remove
Keith> the warnings. gcc 3.2.3, binutils 2.14.90.0.4.
Keith> {standard input}: Assembler messages: {standard input}:2217:
Keith> Warning: Use of 'tbit.z' violates WAW dependency 'PR%, % in 1
Keith> - 15' (impliedf), specific resource number is 14 {standard
Keith> input}:2217: Warning: Only the first path encountering the
Keith> conflict is reported {standard input}:2211: Warning: This is
Keith> the location of the conflicting usage
Hmmh, in my opinion GCC should put a stop-bit when using a register
after an "asm" that marks that register as "clobbered". For now, I
put an explicit stop-bit after the McKinley spinlock versions (the
Merced ones should be OK because they already have a stop-bit after
writing p14). We should still sort out why GCC doesn't get this
right.
--david
next prev parent reply other threads:[~2004-03-16 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 0:24 [patch] 2.6.4 remove intermittent warnings from spinlock code Keith Owens
2004-03-16 7:34 ` David Mosberger [this message]
2004-03-16 14:54 ` Matthew Wilcox
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=16470.44563.416335.867593@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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