Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935257AbXHOUzP (ORCPT ); Wed, 15 Aug 2007 16:55:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1765737AbXHOUyw (ORCPT ); Wed, 15 Aug 2007 16:54:52 -0400 Received: from gate.crashing.org ([63.228.1.57]:50003 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757898AbXHOUyu (ORCPT ); Wed, 15 Aug 2007 16:54:50 -0400 In-Reply-To: <20070815201748.GN9645@linux.vnet.ibm.com> References: <20070815081841.GA16551@osiris.boeblingen.de.ibm.com> <46C30540.2070603@s5r6.in-berlin.de> <20070815145207.GA23106@gondor.apana.org.au> <46C3253F.5090707@s5r6.in-berlin.de> <20070815162722.GD9645@linux.vnet.ibm.com> <20070815185724.GH9645@linux.vnet.ibm.com> <20070815201748.GN9645@linux.vnet.ibm.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <96f3fa3929d873263891fefadb222431@kernel.crashing.org> Content-Transfer-Encoding: 7bit Cc: horms@verge.net.au, Stefan Richter , Satyam Sharma , Linux Kernel Mailing List , rpjday@mindspring.com, netdev@vger.kernel.org, ak@suse.de, cfriesen@nortel.com, Heiko Carstens , jesper.juhl@gmail.com, linux-arch@vger.kernel.org, Andrew Morton , zlynx@acm.org, clameter@sgi.com, schwidefsky@de.ibm.com, Chris Snook , Herbert Xu , davem@davemloft.net, Linus Torvalds , wensong@linux-vs.org, wjiang@resilience.com From: Segher Boessenkool Subject: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures Date: Wed, 15 Aug 2007 22:52:53 +0200 To: paulmck@linux.vnet.ibm.com X-Mailer: Apple Mail (2.623) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1496 Lines: 38 >> I think this was just terminology confusion here again. Isn't "any >> code >> that it cannot currently see" the same as "another compilation unit", >> and wouldn't the "compilation unit" itself expand if we ask gcc to >> compile more than one unit at once? Or is there some more specific >> "definition" for "compilation unit" (in gcc lingo, possibly?) > > This is indeed my understanding -- "compilation unit" is whatever the > compiler looks at in one go. I have heard the word "module" used for > the minimal compilation unit covering a single .c file and everything > that it #includes, but there might be a better name for this. Yes, that's what's called "compilation unit" :-) [/me double checks] Erm, the C standard actually calls it "translation unit". To be exact, to avoid any more confusion: 5.1.1.1/1: A C program need not all be translated at the same time. The text of the program is kept in units called source files, (or preprocessing files) in this International Standard. A source file together with all the headers and source files included via the preprocessing directive #include is known as a preprocessing translation unit. After preprocessing, a preprocessing translation unit is called a translation unit. Segher - 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/