From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Friesen Subject: Re: [ACPI] Re: Linux 2.4.26-rc1 (cmpxchg vs 80386 build) Date: Tue, 30 Mar 2004 11:42:01 -0500 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <4069A359.7040908@nortelnetworks.com> References: <1080535754.16221.188.camel@dhcppc4> <20040329052238.GD1276@alpha.home.local> <1080598062.983.3.camel@dhcppc4> <1080651370.25228.1.camel@dhcp23.swansea.linux.org.uk> <20040330142215.GA21931@alpha.home.local> <20040330150949.GA22073@alpha.home.local> <20040330161431.GA22272@alpha.home.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040330161431.GA22272@alpha.home.local> To: Willy Tarreau Cc: "Richard B. Johnson" , Alan Cox , Len Brown , Arkadiusz Miskiewicz , Marcelo Tosatti , Linux Kernel Mailing List , ACPI Developers List-Id: linux-acpi@vger.kernel.org Willy Tarreau wrote: > In what I described, a 386 target would be compiled with -march=i386, > but the cmpxchg() FUNCTION will still reference the cmpxchg op-code > in the __asm__ statement, and this is perfectly valid. In this case, > only callers of the cmpxchg() FUNCTION will have a chance to use it. > And at the moment, the only client seems to be ACPI. Will the assembler even let you compile the cmpxchg asm instruction if you're building for i386? Chris