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/95743] [9/10/11 Regression] bogus recursive call to nonrecursive procedure with -fcheck=recursion Date: Mon, 29 Jun 2020 21:13:54 +0000 [thread overview] Message-ID: <bug-95743-4-I87BbT2m2l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95743-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95743 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Thomas Kथà¤nig <tkoenig@gcc.gnu.org>: https://gcc.gnu.org/g:95cdcf701dad826f225d6413b59650f181954399 commit r11-1719-g95cdcf701dad826f225d6413b59650f181954399 Author: Thomas Koenig <tkoenig@gcc.gnu.org> Date: Mon Jun 29 23:11:06 2020 +0200 Do not generate recursion check for compiler-generated procedures. This one-line fix removes a check for recursion for procedures which are compiler-generated, such as finalizers or deallocation. These need to be recursive, even if the user code should not be. gcc/fortran/ChangeLog: PR fortran/95743 * trans-decl.c (gfc_generate_function_code): Do not generate recursion check for compiler-generated procedures.
next prev parent reply other threads:[~2020-06-29 21:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-18 13:54 [Bug fortran/95743] New: [9/10 " antoine.lemoine@bordeaux-inp.fr 2020-06-19 7:11 ` [Bug fortran/95743] " rguenth at gcc dot gnu.org 2020-06-28 12:44 ` tkoenig at gcc dot gnu.org 2020-06-29 20:35 ` [Bug fortran/95743] [9/10/11 " tkoenig at gcc dot gnu.org 2020-06-29 21:13 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-30 13:03 ` cvs-commit at gcc dot gnu.org 2020-06-30 13:50 ` cvs-commit at gcc dot gnu.org 2020-06-30 13:51 ` tkoenig 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-95743-4-I87BbT2m2l@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).