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/98016] Host association problem Date: Sat, 05 Dec 2020 14:14:44 +0000 [thread overview] Message-ID: <bug-98016-4-UXInPJyvSH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98016-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98016 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>: https://gcc.gnu.org/g:7ae210d5db5eb96989b2f639e65678b5597e61f0 commit r11-5759-g7ae210d5db5eb96989b2f639e65678b5597e61f0 Author: Paul Thomas <pault@gcc.gnu.org> Date: Sat Dec 5 14:14:19 2020 +0000 Fortran: flag formal argument before resolving an array spec [PR98016]. 2020-12-05 Paul Thomas <pault@gcc.gnu.org> gcc/fortran PR fortran/98016 * resolve.c (resolve_symbol): Set formal_arg_flag before resolving an array spec and restore value afterwards. gcc/testsuite/ PR fortran/98016 * gfortran.dg/pr98016.f90: New test.
next prev parent reply other threads:[~2020-12-05 14:14 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-26 12:23 [Bug fortran/98016] New: " juergen.reuter at desy dot de 2020-11-26 13:02 ` [Bug fortran/98016] " tkoenig at gcc dot gnu.org 2020-11-26 14:43 ` juergen.reuter at desy dot de 2020-11-26 14:48 ` juergen.reuter at desy dot de 2020-11-26 15:13 ` dominiq at lps dot ens.fr 2020-11-26 17:33 ` kargl at gcc dot gnu.org 2020-11-29 16:08 ` pault at gcc dot gnu.org 2020-12-01 10:58 ` drikosev at gmail dot com 2020-12-03 13:34 ` pault at gcc dot gnu.org 2020-12-05 14:14 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-05 14:16 ` pault 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-98016-4-UXInPJyvSH@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).