From mboxrd@z Thu Jan 1 00:00:00 1970 From: kyle@mcmartin.ca (Kyle McMartin) Subject: Re: [parisc-linux] memory barriers, spinlocks, debuglocks, oh my Date: Mon, 30 Aug 2004 00:14:19 -0400 Message-ID: <20040830041419.GA12022@mcmartin.ca> References: <20040827163701.GA2414@mcmartin.ca> <20040828221524.GT2414@mcmartin.ca> <4132001E.6060707@tiscali.be> <20040829161318.GU2414@mcmartin.ca> <20040830040635.GA18211@colo.lackof.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: parisc-linux@lists.parisc-linux.org To: Grant Grundler Return-Path: In-Reply-To: <20040830040635.GA18211@colo.lackof.org> List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: parisc-linux-bounces@lists.parisc-linux.org On Sun, Aug 29, 2004 at 10:06:35PM -0600, Grant Grundler wrote: > I think you missed Joel's point. > Where does SPIN_UNLOCK set the register that it stores to 1? > Eh, that's what the "r" (...) does. As I understand it, GCC will have the value inside the brackets loaded into a register (in this case, %1 which can be any general register) when the execution path gets to the assembler. AIUI, the syntax is asm(" /* assembler */ " : output : input : clobbers ); Cheers, -- Kyle McMartin _______________________________________________ parisc-linux mailing list parisc-linux@lists.parisc-linux.org http://lists.parisc-linux.org/mailman/listinfo/parisc-linux