public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108957] New: Fortran FE memleak with interfaces
Date: Mon, 27 Feb 2023 22:15:27 +0000 [thread overview]
Message-ID: <bug-108957-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108957
Bug ID: 108957
Summary: Fortran FE memleak with interfaces
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: anlauf at gcc dot gnu.org
Target Milestone: ---
The frontend leaks memory for the following sample:
module m
interface
subroutine s ()
end
end interface
end
==7949== 3,176 (2,792 direct, 384 indirect) bytes in 1 blocks are definitely
lost in loss record 160 of 174
==7949== at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7949== by 0x2E5B904: xcalloc (xmalloc.c:164)
==7949== by 0xC6C174: gfc_get_namespace(gfc_namespace*, int)
(symbol.cc:2875)
==7949== by 0xC12CB0: parse_interface (parse.cc:3789)
==7949== by 0xC12CB0: parse_spec(gfc_statement) (parse.cc:4150)
==7949== by 0xC173D8: parse_module() (parse.cc:6531)
==7949== by 0xC17851: gfc_parse_file() (parse.cc:6842)
==7949== by 0xC76E02: gfc_be_parse_file() (f95-lang.cc:229)
==7949== by 0x14F78AB: compile_file() (toplev.cc:444)
==7949== by 0x14FA80B: do_compile(bool) (toplev.cc:2125)
==7949== by 0x14FABD4: toplev::main(int, char**) (toplev.cc:2277)
==7949== by 0x2D9DE05: main (main.cc:39)
next reply other threads:[~2023-02-27 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 22:15 anlauf at gcc dot gnu.org [this message]
2023-03-06 18:46 ` [Bug fortran/108957] " mikael at gcc dot gnu.org
2023-03-06 18:55 ` mikael at gcc dot gnu.org
2023-03-08 20:29 ` anlauf at gcc dot gnu.org
2023-09-07 20:20 ` anlauf at gcc dot gnu.org
2023-09-08 8:12 ` mikael at gcc dot gnu.org
2023-09-15 11:43 ` cvs-commit at gcc dot gnu.org
2023-09-15 17:24 ` mikael at gcc dot gnu.org
2023-09-15 17:25 ` mikael at gcc dot gnu.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-108957-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).