Re: [patch] dwarf2out crash: missing GTY? (PR 50806)

2011/10/20 Jan Kratochvil : > Hi, > > with custom patched dwarf2out.c I got a crash on memory mangled by the garbage > collector.  With patched GTY there the crash no longer happened - but I do not > have a reproducer anymore, sorry if it is a bogus patch. > > The memory corrupted later was initial

Re: [PATCH, i386, PR50766] Fix incorrect mem/reg operands order

Thanks! K On Fri, Oct 21, 2011 at 12:37 AM, H.J. Lu wrote: > On Thu, Oct 20, 2011 at 1:30 AM, Kirill Yukhin > wrote: >>> >>> OK. >>> >>> Thanks, >>> Uros. >> >> Great, >> could anybody please commit that? >> > > I checked it in for you. > > -- > H.J. >

Re: [patch] dwarf2out crash: missing GTY? (PR 50806)

On Fri, 21 Oct 2011 05:37:09 +0200, Laurynas Biveinis wrote: > This patch is a no-op, as already pointed out. If this comes up again, > I'd set a conditional breakpoint on ggc_set_mark if (arg == struct > dw_loc_list_struct with the field that gets collected) and try to find > out why the field doe

Updated ggc anti fragmentation patchkit

I added a special fragmentation fallback to ggc-page to address the earlier review comments. -Andi

[PATCH 2/3] 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

[PATCH 3/3] Add a fragmentation fallback in ggc-page

From: Andi Kleen There were some concerns that the earlier munmap patch could lead to address space being freed that cannot be allocated again by ggc due to fragmentation. This patch adds a fragmentation fallback to solve this: when a GGC_QUIRE_SIZE sized allocation fails, try again with a page s

[PATCH 1/3] 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

Re: [PATCH 3/3] Add a fragmentation fallback in ggc-page

On Fri, Oct 21, 2011 at 07:52:50AM +0200, Andi Kleen wrote: > @@ -776,13 +778,18 @@ alloc_page (unsigned order) >extras on the freelist. (Can only do this optimization with >mmap for backing store.) */ >struct page_entry *e, *f = G.free_pages; > - int i; > + int

<    1   2