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/101349] ICE in gfc_get_descriptor_field, at fortran/trans-array.c:140 Date: Mon, 30 Aug 2021 20:42:56 +0000 [thread overview] Message-ID: <bug-101349-4-7W9C1PLsMG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101349-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101349 --- Comment #4 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:9213ff13247739d6d335064a6b568278a872a991 commit r12-3230-g9213ff13247739d6d335064a6b568278a872a991 Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Aug 30 22:41:01 2021 +0200 Fortran - correct check for constraint F2008:C628 / F2018:C932 gcc/fortran/ChangeLog: PR fortran/101349 * resolve.c (resolve_allocate_expr): An unlimited polymorphic argument to ALLOCATE must be ALLOCATABLE or a POINTER. Fix the corresponding check. gcc/testsuite/ChangeLog: PR fortran/101349 * gfortran.dg/unlimited_polymorphic_33.f90: New test.
next prev parent reply other threads:[~2021-08-30 20:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-06 17:35 [Bug fortran/101349] New: " gscfq@t-online.de 2021-07-06 18:32 ` [Bug fortran/101349] " kargl at gcc dot gnu.org 2021-08-30 19:31 ` anlauf at gcc dot gnu.org 2021-08-30 20:03 ` sgk at troutmask dot apl.washington.edu 2021-08-30 20:42 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-30 20:49 ` anlauf at gcc dot gnu.org 2021-09-03 19:18 ` cvs-commit 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-101349-4-7W9C1PLsMG@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).