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/102917] [PDT] KIND and LEN type parameters shall not be restricted to default integer Date: Wed, 27 Oct 2021 19:26:55 +0000 [thread overview] Message-ID: <bug-102917-4-am5mRnWcel@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102917-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102917 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:5782bacacada41c0240f5aceb42dcdf78e7042da commit r11-9191-g5782bacacada41c0240f5aceb42dcdf78e7042da Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Oct 26 20:54:41 2021 +0200 Fortran: do not restrict PDT KIND and LEN type parameters to default integer gcc/fortran/ChangeLog: PR fortran/102917 * decl.c (match_attr_spec): Remove invalid integer kind checks on KIND and LEN attributes of PDTs. gcc/testsuite/ChangeLog: PR fortran/102917 * gfortran.dg/pdt_4.f03: Adjust testcase. (cherry picked from commit cfcb27cfcb1d32b8cf7bc463cc1fc5cacae8d199)
next prev parent reply other threads:[~2021-10-27 19:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-24 18:48 [Bug fortran/102917] New: " anlauf at gcc dot gnu.org 2021-10-24 18:49 ` [Bug fortran/102917] " anlauf at gcc dot gnu.org 2021-10-24 19:01 ` anlauf at gcc dot gnu.org 2021-10-26 18:55 ` cvs-commit at gcc dot gnu.org 2021-10-27 19:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-27 19:30 ` 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-102917-4-am5mRnWcel@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).