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/97723] type bound ASSIGNMENT(=) within select rank block wrongly rejected Date: Fri, 10 Sep 2021 20:16:51 +0000 [thread overview] Message-ID: <bug-97723-4-DwqIEjGMxe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97723-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97723 --- 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:25d45b5dd41a9ab005a5ae8ee8e54be17f2467a2 commit r10-10109-g25d45b5dd41a9ab005a5ae8ee8e54be17f2467a2 Author: Paul Thomas <pault@gcc.gnu.org> Date: Sun Dec 27 14:59:38 2020 +0000 Fortran: Fix some select rank issues [PR97694 and 97723]. 2020-12-27 Paul Thomas <pault@gcc.gnu.org> gcc/fortran PR fortran/97694 PR fortran/97723 * check.c (allocatable_check): Select rank temporaries are permitted even though they are treated as associate variables. * resolve.c (gfc_resolve_code): Break on select rank as well as select type so that the block os resolved. * trans-stmt.c (trans_associate_var): Class associate variables that are optional dummies must use the backend_decl. gcc/testsuite/ PR fortran/97694 PR fortran/97723 * gfortran.dg/select_rank_5.f90: New test. (cherry picked from commit c4a678981572c12d158709ace0d3f23dd04cf217)
next prev parent reply other threads:[~2021-09-10 20:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-05 7:20 [Bug fortran/97723] New: " mscfd at gmx dot net 2020-12-10 15:57 ` [Bug fortran/97723] " pault at gcc dot gnu.org 2020-12-10 15:58 ` pault at gcc dot gnu.org 2020-12-10 16:28 ` pault at gcc dot gnu.org 2020-12-11 13:53 ` pault at gcc dot gnu.org 2020-12-11 18:01 ` dominiq at lps dot ens.fr 2020-12-27 14:59 ` cvs-commit at gcc dot gnu.org 2021-09-10 20:16 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-10 20:23 ` 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-97723-4-DwqIEjGMxe@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).