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/68800] Fortran FE produces many memory leaks
Date: Fri, 24 Feb 2023 20:45:30 +0000 [thread overview]
Message-ID: <bug-68800-4-4qHwDhEgdk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68800-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68800
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #7 from anlauf at gcc dot gnu.org ---
gfortran.dg/gomp/associate1.f90 is another candidate showing one of the
tracebacks as in comment#0, even without -fopenmp:
==5113== 224 bytes in 1 blocks are definitely lost in loss record 276 of 356
==5113== at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5113== by 0x205F054: xcalloc (xmalloc.c:164)
==5113== by 0x8F891F: gfc_get_expr() (expr.cc:49)
==5113== by 0x96ED01: gfc_match_rvalue(gfc_expr**) (primary.cc:3831)
==5113== by 0x9338DE: match_primary (matchexp.cc:157)
==5113== by 0x9338DE: match_level_1 (matchexp.cc:211)
==5113== by 0x9338DE: match_mult_operand(gfc_expr**) (matchexp.cc:267)
==5113== by 0x933C18: match_add_operand(gfc_expr**) (matchexp.cc:356)
==5113== by 0x933F0F: match_level_2(gfc_expr**) (matchexp.cc:480)
==5113== by 0x9340D6: match_level_3(gfc_expr**) (matchexp.cc:551)
==5113== by 0x934212: match_level_4 (matchexp.cc:599)
==5113== by 0x934212: match_and_operand(gfc_expr**) (matchexp.cc:693)
==5113== by 0x9343F6: match_or_operand(gfc_expr**) (matchexp.cc:722)
==5113== by 0x934506: match_equiv_operand(gfc_expr**) (matchexp.cc:765)
==5113== by 0x934618: match_level_5(gfc_expr**) (matchexp.cc:811)
==5113==
==5113== 3,232 (672 direct, 2,560 indirect) bytes in 3 blocks are definitely
lost in loss record 322 of 356
==5113== at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5113== by 0x205F054: xcalloc (xmalloc.c:164)
==5113== by 0x8F891F: gfc_get_expr() (expr.cc:49)
==5113== by 0x96EABE: gfc_match_rvalue(gfc_expr**) (primary.cc:3579)
==5113== by 0x9338DE: match_primary (matchexp.cc:157)
==5113== by 0x9338DE: match_level_1 (matchexp.cc:211)
==5113== by 0x9338DE: match_mult_operand(gfc_expr**) (matchexp.cc:267)
==5113== by 0x933C18: match_add_operand(gfc_expr**) (matchexp.cc:356)
==5113== by 0x933F0F: match_level_2(gfc_expr**) (matchexp.cc:480)
==5113== by 0x9340D6: match_level_3(gfc_expr**) (matchexp.cc:551)
==5113== by 0x934212: match_level_4 (matchexp.cc:599)
==5113== by 0x934212: match_and_operand(gfc_expr**) (matchexp.cc:693)
==5113== by 0x9343F6: match_or_operand(gfc_expr**) (matchexp.cc:722)
==5113== by 0x934506: match_equiv_operand(gfc_expr**) (matchexp.cc:765)
==5113== by 0x934618: match_level_5(gfc_expr**) (matchexp.cc:811)
==5113==
==5113== 4,864 (448 direct, 4,416 indirect) bytes in 2 blocks are definitely
lost in loss record 329 of 356
==5113== at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5113== by 0x205F054: xcalloc (xmalloc.c:164)
==5113== by 0x8F891F: gfc_get_expr() (expr.cc:49)
==5113== by 0x96ED72: gfc_match_rvalue(gfc_expr**) (primary.cc:3816)
==5113== by 0x9338DE: match_primary (matchexp.cc:157)
==5113== by 0x9338DE: match_level_1 (matchexp.cc:211)
==5113== by 0x9338DE: match_mult_operand(gfc_expr**) (matchexp.cc:267)
==5113== by 0x933C18: match_add_operand(gfc_expr**) (matchexp.cc:356)
==5113== by 0x933F0F: match_level_2(gfc_expr**) (matchexp.cc:480)
==5113== by 0x9340D6: match_level_3(gfc_expr**) (matchexp.cc:551)
==5113== by 0x934212: match_level_4 (matchexp.cc:599)
==5113== by 0x934212: match_and_operand(gfc_expr**) (matchexp.cc:693)
==5113== by 0x9343F6: match_or_operand(gfc_expr**) (matchexp.cc:722)
==5113== by 0x934506: match_equiv_operand(gfc_expr**) (matchexp.cc:765)
==5113== by 0x934618: match_level_5(gfc_expr**) (matchexp.cc:811)
next prev parent reply other threads:[~2023-02-24 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-68800-4@http.gcc.gnu.org/bugzilla/>
2021-11-09 20:57 ` cvs-commit at gcc dot gnu.org
2021-11-09 21:31 ` aldot at gcc dot gnu.org
2023-02-24 20:45 ` anlauf at gcc dot gnu.org [this message]
2023-05-08 5:56 ` 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-68800-4-4qHwDhEgdk@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).