From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-466676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 470 invoked by alias); 13 Nov 2014 17:58:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 450 invoked by uid 48); 13 Nov 2014 17:58:32 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/63854] New: Fix memory leaks seen in JIT
Date: Thu, 13 Nov 2014 17:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created
Message-ID: <bug-63854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg01148.txt.bz2

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.