Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753535AbYKGR2t (ORCPT ); Fri, 7 Nov 2008 12:28:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751519AbYKGR2i (ORCPT ); Fri, 7 Nov 2008 12:28:38 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:48668 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751119AbYKGR2h (ORCPT ); Fri, 7 Nov 2008 12:28:37 -0500 Date: Fri, 7 Nov 2008 09:26:43 -0800 From: Andrew Morton To: David Howells Cc: Nicolas Pitre , Mathieu Desnoyers , Linus Torvalds , Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org, Ralf Baechle , benh@kernel.crashing.org, paulus@samba.org, David Miller , Ingo Molnar , Thomas Gleixner , Steven Rostedt , linux-arch@vger.kernel.org Subject: Re: [RFC patch 08/18] cnt32_to_63 should use smp_rmb() Message-Id: <20081107092643.0bd9bb4e.akpm@linux-foundation.org> In-Reply-To: <8509.1226077800@redhat.com> References: <20081107082926.ee3e1efe.akpm@linux-foundation.org> <20081107075003.fa93ccf4.akpm@linux-foundation.org> <20081107003816.9b0f947a.akpm@linux-foundation.org> <20081107052336.652868737@polymtl.ca> <20081107053349.861709786@polymtl.ca> <20081106220530.5b0e3a96.akpm@linux-foundation.org> <25363.1226056819@redhat.com> <8189.1226074915@redhat.com> <8509.1226077800@redhat.com> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1491 Lines: 33 On Fri, 07 Nov 2008 17:10:00 +0000 David Howells wrote: > > Andrew Morton wrote: > > > I'd expect it to behave in the same way as it would if the function was > > implemented out-of-line. > > > > But it occurs to me that the modrobe-doesnt-work thing would happen if > > the function _is_ inlined anyway, so we won't be doing that. > > > > Whatever. Killing this many puppies because gcc may do something so > > bizarrely wrong isn't justifiable. > > With gcc, you get one instance of the static variable from inside a static > (inline or outofline) function per .o file that invokes it, and these do not > merge even though they're common symbols. I asked around and the opinion > seems to be that this is correct C. I suppose it's the equivalent of cutting > and pasting a function between several files - why should the compiler assume > it's the same function in each? > OK, thanks, I guess that makes sense. For static inline. I wonder if `extern inline' or plain old `inline' should change it. It's one of those things I hope I never need to know about, but perhaps we do somewhere have static storage in an inline. Wouldn't surprise me, and I bet that if we do, it's a bug. -- 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/