This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug jit/63854] New: Fix memory leaks seen in JIT


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63854

            Bug ID: 63854
           Summary: Fix memory leaks seen in JIT
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: jit
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dmalcolm at gcc dot gnu.org

Created attachment 33959
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33959&action=edit
Log from valgrind

I'm attaching a log from valgrind on test-factorial.c, running 5 in-process
iterations.

PATH=.:$PATH \
LD_LIBRARY_PATH=. \
LIBRARY_PATH=. \
  valgrind \
    --leak-check=full \
    testsuite/jit/test-factorial.exe 2>&1 | tee test-factorial.valgrind.log

Summary is:
==57820== LEAK SUMMARY:
==57820==    definitely lost: 84,140 bytes in 578 blocks
==57820==    indirectly lost: 257,864 bytes in 3,185 blocks
==57820==      possibly lost: 0 bytes in 0 blocks
==57820==    still reachable: 572,159 bytes in 3,112 blocks
==57820==         suppressed: 0 bytes in 0 blocks

Various things show up as leaking 4 or 5 times; presumably those are
per-invocation leaks that we ought to fix to avoid them affecting jit users.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]