public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: frv compile error in set_pte()
Date: Mon, 04 Sep 2006 13:35:23 +0100	[thread overview]
Message-ID: <30253.1157373323@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060904115845.GP4416@stusta.de>

Adrian Bunk <bunk@stusta.de> wrote:

> > Does your compiler support the 'M' and 'U' constraint modifiers on FRV?
> 
> It's a gcc 4.1.1 from ftp.gnu.org.

I presume this:

	#define set_pte(pteptr, pteval) \
	do {                                                    \
		*(pteptr) = (pteval);                           \
		asm volatile("dcf %M0" :: "U"(*pteptr));        \
	} while(0)

	void jump(unsigned long *ppte, unsigned long pte)
	{
		set_pte(ppte, pte);
	}

Shows the problem.


I was in the process of checking that all the FRV constraint stuff got
upstream, but was stalled by an ICE whilst building the gcc-4.2.  This logged
as gcc bug #28583 and not as yet fixed.

However, I've run the above test program with the xgcc intermediate compiler
built during the compilation of gcc, and that shows the problem you're
reporting.  I'll chase it up.


Meanwhile, if you want to use a working, though older gcc, you can find one in:

	ftp://ftp.ges.redhat.com/private/releng/frv-060512-Fc6734/tools.tar.bz2

David

-- 
VGER BF report: H 0.0672117

  reply	other threads:[~2006-09-04 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03 22:06 frv compile error in set_pte() Adrian Bunk
2006-09-04  9:26 ` David Howells
2006-09-04 11:58   ` Adrian Bunk
2006-09-04 12:35     ` David Howells [this message]
2006-09-05 12:31     ` David Howells
2006-09-05 13:11       ` Adrian Bunk

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=30253.1157373323@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@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