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/92587] [9/10/11 Regression] Compiler is unable to generate finalization wrapper
Date: Mon, 04 Jan 2021 18:22:38 +0000	[thread overview]
Message-ID: <bug-92587-4-bfPX21kmZk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92587-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Tobias Burnus
<burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:6f3f06e431c181d3e51d31f49a2bf0be2944ae93

commit r10-9199-g6f3f06e431c181d3e51d31f49a2bf0be2944ae93
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Dec 17 10:39:09 2020 +0100

    Fortran: Delay vtab generation until after parsing [PR92587]

    gcc/fortran/ChangeLog:

            PR fortran/92587
            * match.c (gfc_match_assignment): Move gfc_find_vtab call from here
...
            * resolve.c (gfc_resolve_code): ... to here.

    gcc/testsuite/ChangeLog:

            PR fortran/92587
            * gfortran.dg/finalize_37.f90: New test.

    (cherry picked from commit ba9fa684053917a07bfa8f4742da0e196e72b9a2)

  parent reply	other threads:[~2021-01-04 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92587-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:59 ` [Bug fortran/92587] [9/10 " jakub at gcc dot gnu.org
2020-12-17  9:39 ` [Bug fortran/92587] [9/10/11 " cvs-commit at gcc dot gnu.org
2021-01-04 18:22 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-04 18:23 ` cvs-commit at gcc dot gnu.org
2021-01-05  7:59 ` burnus at gcc dot gnu.org
2021-01-06 17:30 ` liakhdi at ornl dot gov

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-92587-4-bfPX21kmZk@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).