Messages in this thread | | | 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 |
| |
>> 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/
| |