linux-kernel - Re: frv compile error in set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <30253.1157373323@warthog.cambridge.redhat.com>
Date:	Mon, 04 Sep 2006 13:35:23 +0100
From:	David Howells <dhowells@...hat.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	David Howells <dhowells@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: frv compile error in set_pte() 

Adrian Bunk <bunk@...sta.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/