public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49282] New: malloc corruption in large lto1-wpa run during inline edge heap resize
Date: Sat, 04 Jun 2011 02:12:00 -0000	[thread overview]
Message-ID: <bug-49282-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49282

           Summary: malloc corruption in large lto1-wpa run during inline
                    edge heap resize
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: andi-gcc@firstfloor.org


A large lto1-wpa run with 20110603 results now in

malloc.c:3551: munmap_chunk: Assertion `ret == 0' failed.

on x86-64-linux.

When I run with MALLOC_CHECK_=2 it seems to get a bit further, but eventually
aborts (and deadlocks because the abort->internal_error handler calls
malloc again)

Here's the original trace for the malloc that aborts (with MALLOC_CHECK_=2)

Any suggestions for patches to try to revert? Note full bisect
is difficult because this run depends on some earlier fixes.

Not uploading a test case currently because it's quite large.

#10 0x00002b236701d4e5 in raise () from /lib64/libc.so.6
#11 0x00002b236701e9b0 in abort () from /lib64/libc.so.6
#12 0x00002b236705df1a in ?? () from /lib64/libc.so.6
#13 0x00002b23670640d7 in ?? () from /lib64/libc.so.6
#14 0x0000000000b2684d in xrealloc (oldmem=Unhandled dwarf expression opcode
0xf3
) at ../../gcc/libiberty/xmalloc.c:179
#15 0x000000000083e528 in vec_heap_o_reserve_1 (vec=0x2b23ea786010,
reserve=Unhandled dwarf ex
pression opcode 0xf3
)
    at ../../gcc/gcc/vec.c:313
#16 0x00000000005ea27f in VEC_inline_edge_summary_t_heap_reserve_exact (
    alloc_=<value optimized out>, vec_=<value optimized out>)
    at ../../gcc/gcc/ipa-inline.h:128
#17 VEC_inline_edge_summary_t_heap_safe_grow (alloc_=<value optimized out>,
    vec_=<value optimized out>) at ../../gcc/gcc/ipa-inline.h:128
#18 VEC_inline_edge_summary_t_heap_safe_grow_cleared (alloc_=<value optimized
out>,
    vec_=<value optimized out>) at ../../gcc/gcc/ipa-inline.h:128
#19 inline_summary_alloc (alloc_=<value optimized out>, vec_=<value optimized
out>)
    at ../../gcc/gcc/ipa-inline-analysis.c:646
#20 0x00000000005ea3c1 in inline_edge_duplication_hook (src=0x2b2499f41680,
    dst=0x2b243e2d7680, data=Unhandled dwarf expression opcode 0xf3
) at ../../gcc/gcc/ipa-inline-analysis.c:853
#21 0x00000000004e995c in cgraph_call_edge_duplication_hooks
(cs2=0x2b243e2d7680,
    cs1=0x2b2499f41680) at ../../gcc/gcc/cgraph.c:376
#22 cgraph_clone_edge (cs2=0x2b243e2d7680, cs1=0x2b2499f41680) at
../../gcc/gcc/cgraph.c:2127
#23 0x00000000004e9c1d in cgraph_clone_node (n=0x2b2499f286f0,
decl=0x2b2395b15500, count=Unha
ndled dwarf expression opcode 0xf3
)
    at ../../gcc/gcc/cgraph.c:2196
#24 0x00000000005eeb9f in clone_inlined_nodes (e=0x2b2499f4a6e8, duplicate=1
'\001',
    update_original=1 '\001', overall_size=0x102e488)


             reply	other threads:[~2011-06-04  2:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04  2:12 andi-gcc at firstfloor dot org [this message]
2011-06-04 19:56 ` [Bug middle-end/49282] " andi-gcc at firstfloor dot org
2011-06-04 20:58 ` andi-gcc at firstfloor dot org
2011-06-06 10:42 ` rguenth at gcc dot gnu.org
2011-06-06 11:50 ` hubicka at ucw dot cz
2011-06-07  8:15 ` andi-gcc at firstfloor dot org
2011-09-13 12:44 ` hubicka at gcc dot gnu.org
2011-09-13 16:12 ` andi-gcc at firstfloor dot org
2011-10-07  5:50 ` andi-gcc at firstfloor dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-49282-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).