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/95847] [9/10/11 Regression] Internal error when processing pFUnit generated files with --coverage
Date: Thu, 12 Nov 2020 14:42:05 +0000	[thread overview]
Message-ID: <bug-95847-4-iEZlToFnkI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95847-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 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:17563c1153d36440936ea0948ac689f84b2cf666

commit r10-9017-g17563c1153d36440936ea0948ac689f84b2cf666
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Tue Nov 10 10:31:33 2020 +0100

    Fortran: Fix function decl's location [PR95847]

    gcc/fortran/ChangeLog:

            PR fortran/95847
            * trans-decl.c (gfc_get_symbol_decl): Do not (re)set the location
            of an external procedure.
            (build_entry_thunks, generate_coarray_init, create_main_function,
            gfc_generate_function_code): Use fndecl's location in BIND_EXPR.

    gcc/testsuite/ChangeLog:

            PR fortran/95847
            * gfortran.dg/coverage.f90: New test.

    (cherry picked from commit 2d59593105d3b1e38e49f96b74fd81e4e5038c7f)

  parent reply	other threads:[~2020-11-12 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 19:11 [Bug fortran/95847] New: " olebole at debian dot org
2020-06-23 21:07 ` [Bug gcov-profile/95847] " dominiq at lps dot ens.fr
2020-06-24  6:53 ` [Bug gcov-profile/95847] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-11-03 16:47 ` johannes.ziegenbalg at mailbox dot org
2020-11-03 16:48 ` johannes.ziegenbalg at mailbox dot org
2020-11-03 18:06 ` marxin at gcc dot gnu.org
2020-11-05 17:08 ` [Bug fortran/95847] " marxin at gcc dot gnu.org
2020-11-05 19:51 ` kargl at gcc dot gnu.org
2020-11-05 22:29 ` burnus at gcc dot gnu.org
2020-11-10  9:31 ` cvs-commit at gcc dot gnu.org
2020-11-12 13:21 ` burnus at gcc dot gnu.org
2020-11-12 14:42 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-12 15:41 ` cvs-commit at gcc dot gnu.org
2020-11-12 15:43 ` burnus 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-95847-4-iEZlToFnkI@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).