lkml.org 
[lkml]   [2007]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    Date
    >>> What you probably mean is that the compiler has to assume any code
    >>> it cannot currently see can do anything (insofar as allowed by the
    >>> relevant standards etc.)
    >
    > I think this was just terminology confusion here again. Isn't "any code
    > that it cannot currently see" the same as "another compilation unit",

    It is not; try gcc -combine or the upcoming link-time optimisation
    stuff, for example.

    > 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?)

    "compilation unit" is a C standard term. It typically boils down
    to "single .c file".


    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/

    \
     
     \ /
      Last update: 2007-08-15 22:51    [W:0.021 / U:89.748 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site