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/93423] [8/9/10/11 Regression] ICE on invalid with argument list for module procedure
Date: Fri, 18 Sep 2020 20:19:34 +0000	[thread overview]
Message-ID: <bug-93423-4-Nop4vkVVhN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93423-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:13421890f81844acb134a460eda7132db3e504ed

commit r10-8775-g13421890f81844acb134a460eda7132db3e504ed
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Sep 17 14:01:09 2020 +0200

    Fortran: Avoid double-free with parse error (PR96041, PR93423)

    gcc/fortran/

            PR fortran/96041
            PR fortran/93423
            * decl.c (gfc_match_submod_proc): Avoid later double-free
            in the error case.

    (cherry picked from commit c12facd22881517127ebbe213d7ecc7fc1fcea4e)

  parent reply	other threads:[~2020-09-18 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93423-4@http.gcc.gnu.org/bugzilla/>
2020-06-25 20:58 ` anlauf at gcc dot gnu.org
2020-07-02 18:48 ` cvs-commit at gcc dot gnu.org
2020-07-04 17:19 ` anlauf at gcc dot gnu.org
2020-07-07 14:05 ` marxin at gcc dot gnu.org
2020-09-17 12:01 ` cvs-commit at gcc dot gnu.org
2020-09-17 12:07 ` burnus at gcc dot gnu.org
2020-09-18 20:19 ` cvs-commit at gcc dot gnu.org
2020-09-18 20:19 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-19 18:32 ` cvs-commit at gcc dot gnu.org
2020-09-19 18:32 ` cvs-commit at gcc dot gnu.org
2020-09-19 18:42 ` cvs-commit at gcc dot gnu.org
2020-09-19 18:42 ` cvs-commit at gcc dot gnu.org
2020-09-19 18:44 ` anlauf 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-93423-4-Nop4vkVVhN@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).