From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Len Brown <len.brown@intel.com>,
Arkadiusz Miskiewicz <arekm@pld-linux.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: Linux 2.4.26-rc1 (cmpxchg vs 80386 build)
Date: Tue, 30 Mar 2004 11:42:01 -0500 [thread overview]
Message-ID: <4069A359.7040908@nortelnetworks.com> (raw)
In-Reply-To: <20040330161431.GA22272@alpha.home.local>
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
next prev parent reply other threads:[~2004-03-30 16:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F6939@hdsmsx402.hd.intel.com>
[not found] ` <A6974D8E5F98D511BB910002A50A6647615F6939-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-03-29 4:49 ` Linux 2.4.26-rc1 (cmpxchg vs 80386 build) Len Brown
[not found] ` <1080535754.16221.188.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-29 0:09 ` Andi Kleen
2004-03-29 5:22 ` Willy Tarreau
2004-03-29 7:01 ` Denis Vlasenko
[not found] ` <200403290901.47695.vda-so6tiL4DrmS23Ynj82S0jdyBExgiH1vWcG62WxB9dV4@public.gmane.org>
2004-03-29 9:56 ` Arkadiusz Miskiewicz
[not found] ` <200403291156.38961.arekm-k0Z414SquRyhPH1hqNUYSQ@public.gmane.org>
2004-03-29 11:31 ` Alan Cox
2004-03-29 19:57 ` Willy Tarreau
[not found] ` <20040329052238.GD1276-HkMpAodKYdnXX8ko2wsARw@public.gmane.org>
2004-03-29 11:05 ` Frank Mehnert
2004-03-29 22:07 ` Len Brown
2004-03-30 12:56 ` [ACPI] " Alan Cox
2004-03-30 13:15 ` Richard B. Johnson
2004-03-30 14:22 ` Willy Tarreau
2004-03-30 14:48 ` Richard B. Johnson
2004-03-30 15:09 ` Willy Tarreau
[not found] ` <20040330150949.GA22073-HkMpAodKYdnXX8ko2wsARw@public.gmane.org>
2004-03-30 15:33 ` Richard B. Johnson
2004-03-30 16:14 ` [ACPI] " Willy Tarreau
2004-03-30 16:42 ` Chris Friesen [this message]
[not found] ` <4069A359.7040908-hwFIcccggHZv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2004-03-30 17:44 ` Len Brown
2004-03-30 18:30 ` [ACPI] " Arkadiusz Miskiewicz
2004-03-30 20:05 ` Len Brown
2004-03-30 20:25 ` Arkadiusz Miskiewicz
2004-03-30 21:49 ` Len Brown
2004-03-30 20:08 ` Bill Davidsen
[not found] ` <4069D3D2.2020402-sQDSfeB7uhw@public.gmane.org>
2004-03-31 11:13 ` Maciej W. Rozycki
2004-03-31 13:04 ` [ACPI] " Bill Davidsen
2004-03-31 15:02 ` Jamie Lokier
2004-04-01 12:29 ` Maciej W. Rozycki
2004-04-01 13:17 ` Richard B. Johnson
2004-05-08 10:18 ` Denis Vlasenko
[not found] ` <Pine.LNX.4.55.0404011423070.3675-rsPqkUlH4Vdx0R2ya2r/wqsMm+1xrEX8@public.gmane.org>
2004-04-01 20:46 ` Len Brown
[not found] ` <1080852371.30349.19.camel-D2Zvc0uNKG8@public.gmane.org>
2004-04-02 10:54 ` Maciej W. Rozycki
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=4069A359.7040908@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arekm@pld-linux.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=root@chaos.analogic.com \
--cc=willy@w.ods.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