public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb 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: Tue, 03 Aug 2021 14:37:40 +0000 [thread overview] Message-ID: <bug-101632-4-eGIiNODUw8@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 Janne Blomqvist <jb at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jb at gcc dot gnu.org Depends on| |91413 --- Comment #4 from Janne Blomqvist <jb at gcc dot gnu.org> --- In PR91413 we discussed the issue of stack overflows if recursive is made the default. Some decision and solution on that issue is needed. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91413 [Bug 91413] [F2018]: Procedures are recursive by default; switching from stack to static allocation is not safe
next prev parent reply other threads:[~2021-08-03 14:37 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 [this message] 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 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-eGIiNODUw8@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).