public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108923] New: memory leak of get_intrinsic_dummy_arg result
Date: Fri, 24 Feb 2023 12:28:49 +0000 [thread overview]
Message-ID: <bug-108923-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108923
Bug ID: 108923
Summary: memory leak of get_intrinsic_dummy_arg result
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 quite often (when building SPEC 2017) like
==8707== 128 bytes in 8 blocks are definitely lost in loss record 750 of 935
==8707== at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8707== by 0x1C25680: xcalloc (xmalloc.c:164)
==8707== by 0x73C891: get_intrinsic_dummy_arg (intrinsic.cc:4265)
==8707== by 0x73C891: sort_actual(char const*, gfc_actual_arglist**,
gfc_intrinsic_arg*, locus*) (intrinsic.cc:4433)
==8707== by 0x73CD54: check_specific(gfc_intrinsic_sym*, gfc_expr*, int)
(intrinsic.cc:4774)
==8707== by 0x744F21: gfc_intrinsic_func_interface(gfc_expr*, int)
(intrinsic.cc:5032)
==8707== by 0x79BD57: resolve_unknown_f (resolve.cc:2998)
==8707== by 0x79BD57: resolve_function (resolve.cc:3355)
==8707== by 0x79BD57: gfc_resolve_expr(gfc_expr*) [clone .part.56]
(resolve.cc:7204)
==8707== by 0x79D469: gfc_resolve_expr (resolve.cc:7171)
==8707== by 0x79D469: resolve_operator(gfc_expr*) (resolve.cc:4101)
==8707== by 0x79990F: gfc_resolve_expr(gfc_expr*) [clone .part.56]
(resolve.cc:7197)
==8707== by 0x7A2274: gfc_resolve_expr (resolve.cc:11893)
==8707== by 0x7A2274: gfc_resolve_code(gfc_code*, gfc_namespace*)
(resolve.cc:12004)
==8707== by 0x7A0D4F: gfc_resolve_blocks(gfc_code*, gfc_namespace*)
(resolve.cc:10989)
==8707== by 0x7A10A8: gfc_resolve_code(gfc_code*, gfc_namespace*)
(resolve.cc:11990)
==8707== by 0x7A0D4F: gfc_resolve_blocks(gfc_code*, gfc_namespace*)
(resolve.cc:10989)
next reply other threads:[~2023-02-24 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 12:28 rguenth at gcc dot gnu.org [this message]
2023-02-24 16:38 ` [Bug fortran/108923] " mikael at gcc dot gnu.org
2023-02-24 19:41 ` mikael at gcc dot gnu.org
2023-02-24 19:42 ` mikael at gcc dot gnu.org
2023-02-24 21:14 ` cvs-commit at gcc dot gnu.org
2023-02-24 21:44 ` anlauf at gcc dot gnu.org
2023-02-25 20:38 ` cvs-commit at gcc dot gnu.org
2023-03-03 14:03 ` rguenth at gcc dot gnu.org
2023-03-12 10:48 ` cvs-commit at gcc dot gnu.org
2023-03-12 10:48 ` cvs-commit 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-108923-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).