public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "domob at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/37779] Missing RECURSIVE not detected Date: Sun, 30 Nov 2008 20:38:00 -0000 [thread overview] Message-ID: <20081130203733.15237.qmail@sourceware.org> (raw) In-Reply-To: <bug-37779-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from domob at gcc dot gnu dot org 2008-11-30 20:37 ------- Subject: Bug 37779 Author: domob Date: Sun Nov 30 20:36:10 2008 New Revision: 142299 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142299 Log: 2008-11-30 Daniel Kraft <d@domob.eu> PR fortran/37779 * gfortran.h (struct gfc_entry_list): Fixed typo in comment. * resolve.c (is_illegal_recursion): New method. (resolve_procedure_expression): Use new is_illegal_recursion instead of direct check and handle function symbols correctly. (resolve_actual_arglist): Removed useless recursion check. (resolve_function): Use is_illegal_recursion instead of direct check. (resolve_call): Ditto. 2008-11-30 Daniel Kraft <d@domob.eu> PR fortran/37779 * gfortran.dg/recursive_check_1.f: Changed expected error message to the more general new one. * gfortran.dg/recursive_check_2.f90: Ditto. * gfortran.dg/entry_18.f90: Ditto. * gfortran.dg/recursive_check_4.f03: Do "the same" check also for FUNCTIONS, as this is different in details from SUBROUTINES. * gfortran.dg/recursive_check_6.f03: New test. Added: trunk/gcc/testsuite/gfortran.dg/recursive_check_6.f03 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/gfortran.h trunk/gcc/fortran/resolve.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/entry_18.f90 trunk/gcc/testsuite/gfortran.dg/recursive_check_1.f trunk/gcc/testsuite/gfortran.dg/recursive_check_2.f90 trunk/gcc/testsuite/gfortran.dg/recursive_check_4.f03 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37779
next prev parent reply other threads:[~2008-11-30 20:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-09 7:10 [Bug fortran/37779] New: " burnus at gcc dot gnu dot org 2008-11-15 8:32 ` [Bug fortran/37779] " domob at gcc dot gnu dot org 2008-11-22 19:04 ` burnus at gcc dot gnu dot org 2008-11-22 21:42 ` burnus at gcc dot gnu dot org 2008-11-24 13:13 ` domob at gcc dot gnu dot org 2008-11-30 20:38 ` domob at gcc dot gnu dot org [this message] 2008-11-30 20:41 ` domob at gcc dot gnu dot org 2008-12-01 7:28 ` domob 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=20081130203733.15237.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).