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/107560] ICE in gfc_get_derived_type, at fortran/trans-types.cc:2811
Date: Fri, 24 Mar 2023 21:20:19 +0000	[thread overview]
Message-ID: <bug-107560-4-iRncwlcyee@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107560-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from anlauf at gcc dot gnu.org ---
The BOZ memleak should be fixed with r13-6857-g833233a4aefc99.

There is another FE memleak which is the same for z1.f90 and z2.f90:

==16805== 48 bytes in 1 blocks are definitely lost in loss record 19 of 674
==16805==    at 0x4C39571: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==16805==    by 0x2120D94: xcalloc (xmalloc.c:164)
==16805==    by 0x9AB967: gfc_match_actual_arglist(int, gfc_actual_arglist**,
bool) (primary.cc:1870)
==16805==    by 0x9AFEA2: gfc_match_rvalue(gfc_expr**) (primary.cc:3695)
==16805==    by 0x95F6A6: match_primary(gfc_expr**) (matchexp.cc:157)
==16805==    by 0x95F7C3: match_level_1(gfc_expr**) (matchexp.cc:211)
==16805==    by 0x95F885: match_mult_operand(gfc_expr**) (matchexp.cc:267)
==16805==    by 0x95FA90: match_add_operand(gfc_expr**) (matchexp.cc:356)
==16805==    by 0x95FD50: match_level_2(gfc_expr**) (matchexp.cc:480)
==16805==    by 0x95FEE2: match_level_3(gfc_expr**) (matchexp.cc:551)
==16805==    by 0x95FFE6: match_level_4(gfc_expr**) (matchexp.cc:599)
==16805==    by 0x960279: match_and_operand(gfc_expr**) (matchexp.cc:693)

      parent reply	other threads:[~2023-03-24 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 18:16 [Bug fortran/107560] New: " gscfq@t-online.de
2023-03-24 20:50 ` [Bug fortran/107560] " anlauf at gcc dot gnu.org
2023-03-24 20:59 ` kargl at gcc dot gnu.org
2023-03-24 21:07 ` anlauf at gcc dot gnu.org
2023-03-24 21:20 ` anlauf at gcc dot gnu.org [this message]

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-107560-4-iRncwlcyee@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).