search for: d49165

...ree, I propose to add a nosynch attribute (to indicate that a function does not use (non-relaxed) atomics or otherwise synchronize with any other threads (e.g., perform I/O or, as a practical matter, use volatile accesses). I've posted a patch for the nofree attribute (https://reviews.llvm.org/D49165). nosynch's implementation would be very similar (except instead of looking for calls to free, it would look for uses of non-relaxed atomics, volatile ops, and known functions that are not I/O functions). With both of these attributes (nofree and nosynch), a function argument with the derefere...

...e >> that a function does not use (non-relaxed) atomics or otherwise >> synchronize with any other threads (e.g., perform I/O or, as a practical >> matter, use volatile accesses). >> >> I've posted a patch for the nofree attribute >> (https://reviews.llvm.org/D49165). nosynch's implementation would be >> very similar (except instead of looking for calls to free, it would look >> for uses of non-relaxed atomics, volatile ops, and known functions that >> are not I/O functions). >> >> With both of these attributes (nofree and nos...

...atomics or otherwise > >> synchronize with any other threads (e.g., perform I/O or, as a > practical > >> matter, use volatile accesses). > >> > >> I've posted a patch for the nofree attribute > >> (https://reviews.llvm.org/D49165). nosynch's implementation > would be > >> very similar (except instead of looking for calls to free, it > would look > >> for uses of non-relaxed atomics, volatile ops, and known > functions that > >> are not I/O functions). >...

Hi everyone, clang currently implements the 'flatten' function attribute by marking all calls to not 'noinline' functions with 'always_inline'. In effect, only the first level of calls is inlined, not all calls recursively (like gcc does). We briefly discussed possible solutions on IRC: We could add an equivalent LLVM attribute for functions (e.g. 'flatten'). The