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/95373] [9/10/11 Regression] ICE in build_reference_type, at tree.c:7942
Date: Fri, 05 Jun 2020 21:17:15 +0000	[thread overview]
Message-ID: <bug-95373-4-P6y5Rrmu6p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95373-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:2039ad0eb5261a2e7eb1d3c9da7576a5c370c073

commit r9-8656-g2039ad0eb5261a2e7eb1d3c9da7576a5c370c073
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Thu May 28 22:28:08 2020 +0200

    PR fortran/95373 - ICE in build_reference_type, at tree.c:7942

    The use of KIND, LEN, RE, and IM inquiry references for applicable
intrinsic
    types is valid only for suffienctly new Fortran standards.  Add appropriate
    check.

    2020-05-28  Harald Anlauf  <anlauf@gmx.de>

    gcc/fortran/
            PR fortran/95373
            * primary.c (is_inquiry_ref): Check validity of inquiry
            references against selected Fortran standard.

    gcc/testsuite/
            PR fortran/95373
            * gfortran.dg/pr95373_1.f90: New test.
            * gfortran.dg/pr95373_2.f90: New test.

    (cherry picked from commit 5c715e6a2990cfb6c15acc1ee14219523534ec69)

  parent reply	other threads:[~2020-06-05 21:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 19:01 [Bug fortran/95373] New: " gscfq@t-online.de
2020-05-27 19:11 ` [Bug fortran/95373] " marxin at gcc dot gnu.org
2020-05-27 19:47 ` kargl at gcc dot gnu.org
2020-05-27 20:04 ` anlauf at gcc dot gnu.org
2020-05-27 20:30 ` sgk at troutmask dot apl.washington.edu
2020-05-28  7:37 ` rguenth at gcc dot gnu.org
2020-05-28 20:33 ` cvs-commit at gcc dot gnu.org
2020-05-28 20:39 ` anlauf at gcc dot gnu.org
2020-05-29  9:52 ` clyon at gcc dot gnu.org
2020-05-29 20:51 ` anlauf at gcc dot gnu.org
2020-05-30 19:00 ` cvs-commit at gcc dot gnu.org
2020-05-30 19:02 ` anlauf at gcc dot gnu.org
2020-06-05 21:03 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:03 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:17 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-05 21:17 ` cvs-commit at gcc dot gnu.org
2020-06-05 21:18 ` 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-95373-4-P6y5Rrmu6p@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).