Re: [cxx-mem-model] compare_exchange implementation

On Oct 18, 2011, at 3:25 PM, Andrew MacLeod wrote: > On 10/18/2011 06:07 PM, Jakub Jelinek wrote: >> On Tue, Oct 18, 2011 at 06:03:16PM -0400, Andrew MacLeod wrote: >>> Here's the last of the missing intrinsics. compare_exchange is >>> slightly different than the others since it doesn't map dire

Re: [PATCH] Add an intermediate coverage format for gcov

On Oct 18, 2011, at 4:19 PM, Sharad Singhai wrote: > Okay, I liked the idea of self-descriptive tags. I have updated the > patch based on your suggestions. I have simplified the format > somewhat. Instead of repeating function name, I use a 'function' tag > with the format > > function:,, Sound

Re: [google] Suppress FDO-use related notes/warnings (issue5294043)

Got a bad patch for profile. Thanks to David for catching this. Here is the correct one: 2011-10-18   Rong Xu          * gcc/common.opt (fprofile-use-verbose): New flag.        * gcc/value-prof.c (check_ic_counter): guard notes by          flag_profile_use_verbose.          (find_func_by_funcdef_

[PATCH 1/2] Add missing page rounding of a page_entry

From: Andi Kleen This one place in ggc forgot to round page_entry->bytes to the next page boundary, which lead to all the heuristics in freeing to check for continuous memory failing. Round here too, like all other allocators already do. The memory consumed should be the same for MMAP because the

[PATCH 2/2] Free large chunks in ggc

From: Andi Kleen This implements the freeing back of large chunks in the ggc madvise path Richard Guenther asked for. This way on systems with limited address space malloc() and other allocators still have a chance to get back at some of the memory ggc freed. The fragmented pages are still just

<    1   2