public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/101632] NON_RECURSIVE procedure prefix is unsupported. F2018 defaults to recursive procedures.
Date: Mon, 06 Dec 2021 20:47:47 +0000 [thread overview]
Message-ID: <bug-101632-4-vkseDHgXFH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101632-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101632
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-12-06
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #3)
> Better patch.
That patch produces many regressions in the test suite. Seems we're not ready
yet for RECURSIVE as the default.
Removing or commenting out the hunk
+ /* If neither NON_RECURSIVE nor RECURSIVE has been seen and the F2018
+ standard is in play, then mark the the procedure as recursive. */
+ if ((gfc_option.allow_std & GFC_STD_F2018)
+ && !current_attr.non_recursive && !current_attr.recursive)
+ {
+ if (!gfc_add_recursive (¤t_attr, NULL))
+ goto error;
+ }
+
allows at least parsing of NON_RECURSIVE, while having no effect otherwise.
Still lacking: handling of NON_RECURSIVE in module.c .
next prev parent reply other threads:[~2021-12-06 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 19:11 [Bug fortran/101632] New: " kargl at gcc dot gnu.org
2021-07-26 19:14 ` [Bug fortran/101632] " kargl at gcc dot gnu.org
2021-07-26 19:15 ` kargl at gcc dot gnu.org
2021-07-28 5:08 ` sgk at troutmask dot apl.washington.edu
2021-08-03 14:37 ` jb at gcc dot gnu.org
2021-08-03 15:14 ` sgk at troutmask dot apl.washington.edu
2021-11-06 21:09 ` anlauf at gcc dot gnu.org
2021-12-06 20:47 ` anlauf at gcc dot gnu.org [this message]
2022-04-19 15:53 ` everythingfunctional at protonmail dot com
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-101632-4-vkseDHgXFH@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).