public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99798] ICE when compiling a variant of pr87907
Date: Mon, 20 May 2024 20:44:37 +0000	[thread overview]
Message-ID: <bug-99798-4-LzaKZjk7rB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99798-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Mikael Morin <mikael@gcc.gnu.org>:

https://gcc.gnu.org/g:38d1761c0c94b77a081ccc180d6e039f7a670468

commit r15-698-g38d1761c0c94b77a081ccc180d6e039f7a670468
Author: Mikael Morin <mikael@gcc.gnu.org>
Date:   Sun May 12 15:16:23 2024 +0200

    fortran: Assume there is no cyclic reference with submodule symbols
[PR99798]

    This prevents a premature release of memory with procedure symbols from
    submodules, causing random compiler crashes.

    The problem is a fragile detection of cyclic references, which can match
    with procedures host-associated from a module in submodules, in cases where
it
    shouldn't.  The formal namespace is released, and with it the dummy
arguments
    symbols of the procedure.  But there is no cyclic reference, so the
procedure
    symbol itself is not released and remains, with pointers to its dummy
arguments
    now dangling.

    The fix adds a condition to avoid the case, and refactors to a new
predicate
    by the way.  Part of the original condition is also removed, for lack of a
    reason to keep it.

            PR fortran/99798

    gcc/fortran/ChangeLog:

            * symbol.cc (gfc_release_symbol): Move the condition guarding
            the handling cyclic references...
            (cyclic_reference_break_needed): ... here as a new predicate.
            Remove superfluous parts.  Add a condition preventing any premature
            release with submodule symbols.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/submodule_33.f08: New test.

      parent reply	other threads:[~2024-05-20 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 15:59 [Bug fortran/99798] New: " dominiq at lps dot ens.fr
2021-03-27 20:00 ` [Bug fortran/99798] " anlauf at gcc dot gnu.org
2023-05-28  5:11 ` kargl at gcc dot gnu.org
2023-07-11 14:56 ` mikael at gcc dot gnu.org
2024-05-11 11:27 ` mikael at gcc dot gnu.org
2024-05-20 20:44 ` cvs-commit 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-99798-4-LzaKZjk7rB@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).