public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/26551] gfortran compiles recursive subroutines declared without the RECURSIVE attribute Date: Wed, 17 May 2006 14:12:00 -0000 [thread overview] Message-ID: <20060517141152.14608.qmail@sourceware.org> (raw) In-Reply-To: <bug-26551-12305@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from fxcoudert at gcc dot gnu dot org 2006-05-17 14:11 ------- Subject: Bug 26551 Author: fxcoudert Date: Wed May 17 14:11:40 2006 New Revision: 113860 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113860 Log: PR fortran/26551 * resolve.c (resolve_call, resolve_function): Issue an error if a function or subroutine call is recursive but the function or subroutine wasn't declared as such. * gfortran.dg/recursive_check_1.f: New test. Added: trunk/gcc/testsuite/gfortran.dg/recursive_check_1.f Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26551
next prev parent reply other threads:[~2006-05-17 14:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-03 19:50 [Bug fortran/26551] New: " bdtaylo1 at uiuc dot edu 2006-03-03 20:00 ` [Bug fortran/26551] " pinskia at gcc dot gnu dot org 2006-03-03 20:02 ` pinskia at gcc dot gnu dot org 2006-03-03 21:05 ` bdtaylo1 at uiuc dot edu 2006-05-07 11:08 ` fxcoudert at gcc dot gnu dot org 2006-05-17 14:12 ` fxcoudert at gcc dot gnu dot org [this message] 2006-05-17 14:15 ` fxcoudert at gcc dot gnu dot org 2006-05-27 9:06 ` [Bug fortran/26551] [4.1 only] " fxcoudert at gcc dot gnu dot org 2006-05-27 9:07 ` [Bug fortran/26551] " fxcoudert at gcc dot gnu dot 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=20060517141152.14608.qmail@sourceware.org \ --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).