public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/111781] Fortran compiler complains about variable bound in array dummy argument
Date: Thu, 12 Oct 2023 10:16:03 +0000	[thread overview]
Message-ID: <bug-111781-4-CLtZEThnw8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111781-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111781

Mikael Morin <mikael at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |patch
                 CC|                            |mikael at gcc dot gnu.org
   Last reconfirmed|                            |2023-10-12

--- Comment #1 from Mikael Morin <mikael at gcc dot gnu.org> ---
Confirmed.

This should fix it:

diff --git a/gcc/fortran/resolve.cc b/gcc/fortran/resolve.cc
index 1042b8c18e8..e2e0fc8eba3 100644
--- a/gcc/fortran/resolve.cc
+++ b/gcc/fortran/resolve.cc
@@ -285,6 +285,7 @@ gfc_resolve_formal_arglist (gfc_symbol *proc)
       sym->attr.always_explicit = 1;
     }

+  bool saved_formal_arg_flag = formal_arg_flag;
   formal_arg_flag = true;

   for (f = proc->formal; f; f = f->next)
@@ -533,7 +534,7 @@ gfc_resolve_formal_arglist (gfc_symbol *proc)
            }
        }
     }
-  formal_arg_flag = false;
+  formal_arg_flag = saved_formal_arg_flag;
 }

  reply	other threads:[~2023-10-12 10:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  9:06 [Bug fortran/111781] New: Compiler error on valid code rasmus.vikhamar-sandberg at uit dot no
2023-10-12 10:16 ` mikael at gcc dot gnu.org [this message]
2023-10-21 14:01 ` [Bug fortran/111781] Fortran compiler complains about variable bound in array dummy argument mikael at gcc dot gnu.org
2023-10-21 16:37 ` mikael at gcc dot gnu.org
2024-02-06 18:19 ` anlauf at gcc dot gnu.org
2024-02-28 18:25 ` anlauf at gcc dot gnu.org
2024-02-28 19:38 ` mikael at gcc dot gnu.org
2024-03-15 19:37 ` mikael at gcc dot gnu.org
2024-03-15 19:57 ` anlauf at gcc dot gnu.org
2024-03-15 20:25 ` mikael at gcc dot gnu.org
2024-03-22 12:07 ` cvs-commit at gcc dot gnu.org
2024-03-28 10:40 ` cvs-commit at gcc dot gnu.org
2024-04-02 13:15 ` mikael 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-111781-4-CLtZEThnw8@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: link
Be 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).