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/95614] ICE in build_field, at fortran/trans-common.c:301
Date: Sun, 27 Sep 2020 13:50:15 +0000 [thread overview]
Message-ID: <bug-95614-4-JB2p18LKP8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95614-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95614
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Mark Eggleston
<markeggleston@gcc.gnu.org>:
https://gcc.gnu.org/g:4a67941a956003dcce8866604ba25f5a0bfd16cf
commit r10-8803-g4a67941a956003dcce8866604ba25f5a0bfd16cf
Author: Mark Eggleston <markeggleston@gcc.gnu.org>
Date: Thu Jun 11 14:33:51 2020 +0100
Fortran : ICE in build_field PR95614
Local identifiers can not be the same as a module name. Original
patch by Steve Kargl resulted in name clashes between common block
names and local identifiers. A local identifier can be the same as
a global identier if that identifier represents a common. The patch
was modified to allow global identifiers that represent a common
block.
2020-09-27 Steven G. Kargl <kargl@gcc.gnu.org>
Mark Eggleston <markeggleston@gcc.gnu.org>
gcc/fortran/
PR fortran/95614
* decl.c (gfc_get_common): Use gfc_match_common_name instead
of match_common_name.
* decl.c (gfc_bind_idents): Use gfc_match_common_name instead
of match_common_name.
* match.c : Rename match_common_name to gfc_match_common_name.
* match.c (gfc_match_common): Use gfc_match_common_name instead
of match_common_name.
* match.h : Rename match_common_name to gfc_match_common_name.
* resolve.c (resolve_common_vars): Check each symbol in a
common block has a global symbol. If there is a global symbol
issue an error if the symbol type is known as is not a common
block name.
2020-09-27 Mark Eggleston <markeggleston@gcc.gnu.org>
gcc/testsuite/
PR fortran/95614
* gfortran.dg/pr95614_1.f90: New test.
* gfortran.dg/pr95614_2.f90: New test.
(cherry picked from commit e5a76af3a2f3324efc60b4b2778ffb29d5c377bc)
next prev parent reply other threads:[~2020-09-27 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 17:35 [Bug fortran/95614] New: " gscfq@t-online.de
2020-06-09 17:44 ` [Bug fortran/95614] " dominiq at lps dot ens.fr
2020-06-09 21:41 ` kargl at gcc dot gnu.org
2020-06-22 9:10 ` drikosev at gmail dot com
2020-06-22 15:53 ` sgk at troutmask dot apl.washington.edu
2020-09-27 12:12 ` cvs-commit at gcc dot gnu.org
2020-09-27 13:50 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-27 16:30 ` cvs-commit at gcc dot gnu.org
2020-09-27 17:43 ` cvs-commit at gcc dot gnu.org
2020-09-28 6:29 ` markeggleston at gcc dot gnu.org
2020-09-28 10:14 ` markeggleston at gcc dot gnu.org
2020-10-14 10:08 ` cvs-commit at gcc dot gnu.org
2020-10-14 13:15 ` markeggleston 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-95614-4-JB2p18LKP8@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).