Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Guy Martin <gmsoft@tuxicoman.be>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: kyle@mcmartin.ca (Kyle McMartin),
	dave.anglin@nrc-cnrc.gc.ca, cavokz@gmail.com,
	linux-parisc@vger.kernel.org
Subject: Re: can't find a register in class 'R1_REGS' while reloading 'asm'
Date: Sun, 7 Nov 2010 17:50:42 +0100	[thread overview]
Message-ID: <20101107175042.627060c2@zombie> (raw)
In-Reply-To: <20100208032035.645A14EF1@hiauly1.hia.nrc.ca>


Any update on this ?

I'm still running into the issue with gcc 4.4.4 and linux 2.6.37-rc1.

Regards,
  Guy

On Sun, 7 Feb 2010 22:20:34 -0500 (EST)
"John David Anglin" <dave@hiauly1.hia.nrc.ca> wrote:

> > On Mon, Dec 07, 2009 at 10:01:14PM -0500, John David Anglin wrote:
> > > -	volatile unsigned int *a;
> > > +	volatile register unsigned int *a asm ("r20") =
> > > __ldcw_align(x); 
> > 
> > I'm reticent about moving the assignment around the mb(), should I
> > edit this to return the assignment and apply, or apply as is?
> 
> I don't believe the __ldcw_align operation involves a memory read or
> write.  It's just adjusting a pointer.  Thus moving it past the mb()
> shouldn't matter.  That said, I been wrong before...
> 
> Dave


  reply	other threads:[~2010-11-07 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 22:35 can't find a register in class 'R1_REGS' while reloading 'asm' Domenico Andreoli
2009-12-08  1:26 ` John David Anglin
2009-12-08  3:01   ` John David Anglin
2009-12-16  3:37     ` Kyle McMartin
2009-12-16  4:16       ` John David Anglin
2010-02-07  0:23     ` Kyle McMartin
2010-02-08  3:20       ` John David Anglin
2010-11-07 16:50         ` Guy Martin [this message]
2010-11-07 18:48           ` John David Anglin

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=20101107175042.627060c2@zombie \
    --to=gmsoft@tuxicoman.be \
    --cc=cavokz@gmail.com \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@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