public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.4 remove intermittent warnings from spinlock code
Date: Tue, 16 Mar 2004 14:54:02 +0000	[thread overview]
Message-ID: <20040316145402.GR25059@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <2465.1079310276@kao2.melbourne.sgi.com>

On Mon, Mar 15, 2004 at 11:34:43PM -0800, David Mosberger wrote:
> 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.

I'm not a compiler person, but ...

Seems to me that doing exactly what you're asking for is hard.  Editing
the inline asm to use a stop-bit if the compiler needs to reuse that
register would be a really awful layering violation.  But it shouldn't
be too hard for p14 to be considered unavailable until the next stop
bit has been issued.

Al, want to raise this on the gcc mailing list?

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

      parent reply	other threads:[~2004-03-16 14:54 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
2004-03-16 14:54 ` Matthew Wilcox [this message]

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=20040316145402.GR25059@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --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