Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763088AbXHLGLA (ORCPT ); Sun, 12 Aug 2007 02:11:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752879AbXHLGKt (ORCPT ); Sun, 12 Aug 2007 02:10:49 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:52542 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752522AbXHLGKr (ORCPT ); Sun, 12 Aug 2007 02:10:47 -0400 Date: Sat, 11 Aug 2007 23:09:56 -0700 (PDT) From: Linus Torvalds To: Segher Boessenkool cc: schwidefsky@de.ibm.com, wjiang@resilience.com, wensong@linux-vs.org, heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org, ak@suse.de, cfriesen@nortel.com, netdev@vger.kernel.org, horms@verge.net.au, akpm@linux-foundation.org, Chuck Ebbert , davem@davemloft.net, zlynx@acm.org, Chris Snook Subject: Re: [PATCH] make atomic_t volatile on all architectures In-Reply-To: Message-ID: References: <20070808230733.GA17270@shell.boston.redhat.com> <46BAC2BE.1090106@redhat.com> <46BB508B.7050601@redhat.com> <1186683646.9669.20.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1112 Lines: 29 On Sun, 12 Aug 2007, Segher Boessenkool wrote: > > Note that last line. Segher, how about you just accept that Linux uses gcc as per reality, and that sometimes the reality is different from your expectations? "+m" works. We use it. It's better than the alternatives. Pointing to stale documentation doesn't change anything. The same is true of accesses through a volatile pointer. The kernel has done that for a *loong* time (all MMIO IO is done that way), and it's totally pointless to say that "volatile" isn't guaranteed to do what it does. It works, and quite frankly, if it didn't work, it would be a gcc BUG. And again, this is not a "C standard" issue. It's a "sane implementation" issue. Linux expects the compiler to be sane. If it isn't, that's not our problem. gcc *is* sane, and I don't see why you constantly act as if it wasn't. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/