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/89574] [8/9/10/11 Regression] internal compiler error: in conv_function_val, at fortran/trans-expr.c:3792
Date: Tue, 21 Jul 2020 19:37:51 +0000	[thread overview]
Message-ID: <bug-89574-4-D1TaTxJI4y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89574-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:28f2a080cc27531a8c78aec9f44aeff4961c2a4c

commit r11-2256-g28f2a080cc27531a8c78aec9f44aeff4961c2a4c
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Jul 21 21:37:30 2020 +0200

    PR fortran/89574 - ICE in conv_function_val, at fortran/trans-expr.c:3792

    When checking for an external procedure from the same file, do not
    consider symbols from different modules.

    gcc/fortran/
            PR fortran/89574
            * trans-decl.c (gfc_get_extern_function_decl): Check whether a
            symbol belongs to a different module.

  parent reply	other threads:[~2020-07-21 19:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89574-4@http.gcc.gnu.org/bugzilla/>
2020-07-05 19:42 ` anlauf at gcc dot gnu.org
2020-07-09 20:55 ` anlauf at gcc dot gnu.org
2020-07-14 21:09 ` anlauf at gcc dot gnu.org
2020-07-14 21:21 ` anlauf at gcc dot gnu.org
2020-07-21 19:37 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-23 19:03 ` cvs-commit at gcc dot gnu.org
2020-07-23 19:53 ` cvs-commit at gcc dot gnu.org
2020-07-23 20:03 ` cvs-commit at gcc dot gnu.org
2020-07-23 20:04 ` 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-89574-4-D1TaTxJI4y@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).