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/97491] Wrong restriction for VALUE arguments of pure procedures Date: Tue, 03 Nov 2020 22:01:35 +0000 [thread overview] Message-ID: <bug-97491-4-LR3W7yASOK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97491-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97491 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:a00894a3a3eb2852cd782a9cc6ee5bd83bfff542 commit r10-8970-ga00894a3a3eb2852cd782a9cc6ee5bd83bfff542 Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Oct 27 20:25:23 2020 +0100 PR fortran/97491 - Wrong restriction for VALUE arguments of pure procedures A dummy argument with the VALUE attribute may be redefined in a PURE or ELEMENTAL procedure. Adjust the associated purity check. gcc/fortran/ChangeLog: * resolve.c (gfc_impure_variable): A dummy argument with the VALUE attribute may be redefined without making a procedure impure. gcc/testsuite/ChangeLog: * gfortran.dg/value_8.f90: New test. (cherry picked from commit a764c40079a493826a3678174f908941a383644e)
next prev parent reply other threads:[~2020-11-03 22:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-19 12:40 [Bug fortran/97491] New: " tkoenig at gcc dot gnu.org 2020-10-19 20:26 ` [Bug fortran/97491] " anlauf at gcc dot gnu.org 2020-10-24 21:00 ` anlauf at gcc dot gnu.org 2020-10-26 20:59 ` anlauf at gcc dot gnu.org 2020-10-27 19:40 ` cvs-commit at gcc dot gnu.org 2020-10-27 19:44 ` anlauf at gcc dot gnu.org 2020-11-03 22:01 ` cvs-commit at gcc dot gnu.org [this message] 2020-11-03 22:04 ` anlauf at gcc dot gnu.org 2021-03-16 13:16 ` burnus at gcc dot gnu.org 2021-03-20 20:22 ` 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-97491-4-LR3W7yASOK@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).