public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/68108] [6 regression] erroneous error message 'scalar integer expression expected' Date: Thu, 29 Oct 2015 19:38:00 -0000 [thread overview] Message-ID: <bug-68108-4-mRPCv7wLLb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68108-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68108 --- Comment #8 from kargl at gcc dot gnu.org --- Author: kargl Date: Thu Oct 29 19:37:59 2015 New Revision: 229553 URL: https://gcc.gnu.org/viewcvs?rev=229553&root=gcc&view=rev Log: 2015-10-29 Steven G. Kargl <kargl@gcc.gnu.org> PR fortran/67805 PR fortran/68108 * array.c (gfc_match_array_constructor): Check for error from type spec matching. * decl.c (char_len_param_value): Check for valid of charlen parameter. Check for REF_ARRAY. Reap dead code dating to 2008. match.c (gfc_match_type_spec): Special case the keyword use in REAL. 2015-10-29 Steven G. Kargl <kargl@gcc.gnu.org> PR fortran/67805 PR fortran/68108 * gfortran.dg/pr67805.f90: New testcase. * gfortran.dg/pr67805_2.f90: New test. * gfortran.dg/array_constructor_26.f03: Update testcase. * gfortran.dg/array_constructor_27.f03: Ditto. * gfortran.dg/char_type_len_2.f90: Ditto. * gfortran.dg/pr67802.f90: Ditto. * gfortran.dg/used_before_typed_3.f90: Ditto. Added: branches/gcc-5-branch/gcc/testsuite/gfortran.dg/pr67805.f90 branches/gcc-5-branch/gcc/testsuite/gfortran.dg/pr67805_2.f90 Modified: branches/gcc-5-branch/gcc/fortran/ChangeLog branches/gcc-5-branch/gcc/fortran/array.c branches/gcc-5-branch/gcc/fortran/decl.c branches/gcc-5-branch/gcc/fortran/match.c branches/gcc-5-branch/gcc/testsuite/ChangeLog branches/gcc-5-branch/gcc/testsuite/gfortran.dg/array_constructor_26.f03 branches/gcc-5-branch/gcc/testsuite/gfortran.dg/array_constructor_27.f03 branches/gcc-5-branch/gcc/testsuite/gfortran.dg/char_type_len_2.f90 branches/gcc-5-branch/gcc/testsuite/gfortran.dg/large_real_kind_3.F90 branches/gcc-5-branch/gcc/testsuite/gfortran.dg/pr67802.f90 branches/gcc-5-branch/gcc/testsuite/gfortran.dg/used_before_typed_3.f90
next prev parent reply other threads:[~2015-10-29 19:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-68108-4@http.gcc.gnu.org/bugzilla/> 2015-10-27 9:51 ` rguenth at gcc dot gnu.org 2015-10-27 10:52 ` mikael at gcc dot gnu.org 2015-10-27 10:54 ` mikael at gcc dot gnu.org 2015-10-27 13:44 ` sgk at troutmask dot apl.washington.edu 2015-10-27 16:43 ` kargl at gcc dot gnu.org 2015-10-27 16:48 ` kargl at gcc dot gnu.org 2015-10-29 19:38 ` kargl at gcc dot gnu.org [this message] 2015-10-29 19:41 ` kargl 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-68108-4-mRPCv7wLLb@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: linkBe 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).