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/94397] [9/10/11 Regression] the compiler consider "type is( real(kind(1.)) )" as a syntax error since r10-7369-gc38daa7976886a59
Date: Thu, 28 May 2020 13:45:17 +0000 [thread overview]
Message-ID: <bug-94397-4-5vjMSeyjqM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94397-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94397
--- Comment #11 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:f2fe2ad8d379297dcf571b2b9c46200c5ae5391f
commit r10-8200-gf2fe2ad8d379297dcf571b2b9c46200c5ae5391f
Author: Mark Eggleston <markeggleston@gcc.gnu.org>
Date: Wed Apr 1 09:52:41 2020 +0100
Fortran : "type is( real(kind(1.)) )" spurious syntax error PR94397
Based on a patch in the comments of the PR. That patch fixed this
problem but caused the test cases for PR93484 to fail. It has been
changed to reduce initialisation expressions if the expression is
not EXPR_VARIABLE and not EXPR_CONSTANT.
2020-05-28 Steven G. Kargl <kargl@gcc.gnu.org>
Mark Eggleston <markeggleston@gcc.gnu.org>
gcc/fortran/
PR fortran/94397
* match.c (gfc_match_type_spec): New variable ok initialised
to true. Set ok with the return value of gfc_reduce_init_expr
called only if the expression is not EXPR_CONSTANT and is not
EXPR_VARIABLE. Add !ok to the check for type not being integer
or the rank being greater than zero.
2020-05-28 Mark Eggleston <markeggleston@gcc.gnu.org>
gcc/testsuite/
PR fortran/94397
* gfortran.dg/pr94397.F90: New test.
(cherry picked from commit 3ea6977d0f1813d982743a09660eec1760e981ec)
next prev parent reply other threads:[~2020-05-28 13:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:06 [Bug fortran/94397] New: [10 Regression] the compiler consider "type is( real(kind(1.)) )" as a syntax error chinoune.mehdi at hotmail dot com
2020-03-30 8:29 ` [Bug fortran/94397] " rguenth at gcc dot gnu.org
2020-03-30 8:58 ` marxin at gcc dot gnu.org
2020-03-30 16:23 ` [Bug fortran/94397] [10 Regression] the compiler consider "type is( real(kind(1.)) )" as a syntax error since r10-7369-gc38daa7976886a59 kargl at gcc dot gnu.org
2020-03-30 16:41 ` sgk at troutmask dot apl.washington.edu
2020-03-31 7:12 ` markeggleston at gcc dot gnu.org
2020-03-31 14:33 ` kargl at gcc dot gnu.org
2020-04-01 7:51 ` markeggleston at gcc dot gnu.org
2020-04-29 20:46 ` [Bug fortran/94397] [9/10 " anlauf at gcc dot gnu.org
2020-04-30 6:41 ` markeggleston at gcc dot gnu.org
2020-05-07 11:56 ` [Bug fortran/94397] [9/10/11 " jakub at gcc dot gnu.org
2020-05-28 12:27 ` cvs-commit at gcc dot gnu.org
2020-05-28 13:45 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-28 15:06 ` cvs-commit at gcc dot gnu.org
2020-05-28 15:08 ` 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-94397-4-5vjMSeyjqM@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).