public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44430] [4.5/4.6 Regression] Infinite recursion with -fdump-parse-tree
Date: Sun, 06 Jun 2010 20:52:00 -0000	[thread overview]
Message-ID: <20100606205236.2153.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44430-10391@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from tkoenig at gcc dot gnu dot org  2010-06-06 20:52 -------
I agree.  Rev. 149586 is:

2009-07-13  Janus Weil  <janus@gcc.gnu.org>

       PR fortran/40646
       * module.c (mio_symbol): If the symbol has formal arguments,
       the formal namespace will be present.
       * resolve.c (resolve_actual_arglist): Correctly handle 'called'
       procedure pointer components as actual arguments.
       (resolve_fl_derived,resolve_symbol): Make sure the formal namespace
       is present.
       * trans-expr.c (gfc_conv_procedure_call): Correctly handle the formal
       arguments of procedure pointer components.

(nothing else suspicious in that range.

Janus?


-- 

tkoenig at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |janus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44430


  parent reply	other threads:[~2010-06-06 20:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 10:11 [Bug fortran/44430] New: [4.6 " tkoenig at gcc dot gnu dot org
2010-06-06 10:11 ` [Bug fortran/44430] " tkoenig at gcc dot gnu dot org
2010-06-06 10:32 ` dominiq at lps dot ens dot fr
2010-06-06 11:22 ` [Bug fortran/44430] [4.5/4.6 " tkoenig at gcc dot gnu dot org
2010-06-06 20:15 ` tkoenig at gcc dot gnu dot org
2010-06-06 20:39 ` dominiq at lps dot ens dot fr
2010-06-06 20:52 ` tkoenig at gcc dot gnu dot org [this message]
2010-06-06 21:31 ` janus at gcc dot gnu dot org
2010-06-06 21:46 ` janus at gcc dot gnu dot org
2010-06-06 21:46 ` janus at gcc dot gnu dot org
2010-06-06 21:51 ` janus at gcc dot gnu dot org
2010-06-09 18:38 ` janus at gcc dot gnu dot org
2010-06-12  4:02 ` janus at gcc dot gnu dot org
2010-06-12  4:03 ` janus 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=20100606205236.2153.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: 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).