From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4F0143858284; Fri, 24 Feb 2023 12:31:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4F0143858284
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677241903;
	bh=dM7NwBQ/W13GqzrjxUE5ITM61sSzBCDs6uz5miyYAfE=;
	h=From:To:Subject:Date:From;
	b=JAGZMLOtfFKNRbnv1X3XI7ZKs5UQPKblU4ByThrqiKz6e+zJnaoY9hrXdcwiQmwXY
	 PBglVkmWYlmD7Gus6IoYg2tMk0ugGLBUO1n80Vdf49VXD+/7pQLvIv3L7ZdviAnix8
	 bsaE+VG4o4HD5JaQZ+kZrCeLEGHFVvcQnXU5RYfs=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108924] New: memory leak in doloop_warn
Date: Fri, 24 Feb 2023 12:31:42 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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 target_milestone
Message-ID: <bug-108924-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

            Bug ID: 108924
           Summary: memory leak in doloop_warn
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

valgrind leak check complains

=3D=3D8747=3D=3D 16 bytes in 2 blocks are definitely lost in loss record 6 =
of 2,309
=3D=3D8747=3D=3D    at 0x4C346A4: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
=3D=3D8747=3D=3D    by 0x5697698: __gmp_default_allocate (in
/usr/lib64/libgmp.so.10.3.2)
=3D=3D8747=3D=3D    by 0x56A7A22: __gmpz_init_set (in /usr/lib64/libgmp.so.=
10.3.2)
=3D=3D8747=3D=3D    by 0x874110: do_subscript (frontend-passes.cc:2863)
=3D=3D8747=3D=3D    by 0x874110: do_function(gfc_expr**, int*, void*)
(frontend-passes.cc:2710)
=3D=3D8747=3D=3D    by 0x870675: gfc_expr_walker(gfc_expr**, int (*)(gfc_ex=
pr**, int*,
void*), void*) (frontend-passes.cc:5243)
=3D=3D8747=3D=3D    by 0x870859: gfc_expr_walker(gfc_expr**, int (*)(gfc_ex=
pr**, int*,
void*), void*) (frontend-passes.cc:5250)
=3D=3D8747=3D=3D    by 0x870859: gfc_expr_walker(gfc_expr**, int (*)(gfc_ex=
pr**, int*,
void*), void*) (frontend-passes.cc:5250)
=3D=3D8747=3D=3D    by 0x8727D9: gfc_code_walker(gfc_code**, int (*)(gfc_co=
de**, int*,
void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5680)
=3D=3D8747=3D=3D    by 0x872857: gfc_code_walker(gfc_code**, int (*)(gfc_co=
de**, int*,
void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5687)
=3D=3D8747=3D=3D    by 0x872857: gfc_code_walker(gfc_code**, int (*)(gfc_co=
de**, int*,
void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5687)
=3D=3D8747=3D=3D    by 0x872857: gfc_code_walker(gfc_code**, int (*)(gfc_co=
de**, int*,
void*), int (*)(gfc_expr**, int*, void*), void*) (frontend-passes.cc:5687)
=3D=3D8747=3D=3D    by 0x8738CB: doloop_warn(gfc_namespace*) (frontend-pass=
es.cc:3079)

so it looks like some gmp vars are not released.=