public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36426]  New: Compiling tiny prog: Stack overflow; uses PROCEDURE
Date: Mon, 02 Jun 2008 20:52:00 -0000	[thread overview]
Message-ID: <bug-36426-13404@http.gcc.gnu.org/bugzilla/> (raw)

The following valid program causes gfortran to use more and more stack memory.

abstract interface
  function foo(x)
   character(len=len(x)) :: foo,x
  end function foo
end interface
character(len=20) :: str
procedure(foo) :: bar
str = bar("Hello")
end


-- 
           Summary: Compiling tiny prog: Stack overflow; uses PROCEDURE
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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


             reply	other threads:[~2008-06-02 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 20:52 burnus at gcc dot gnu dot org [this message]
2008-06-07 16:48 ` [Bug fortran/36426] Endless loop in gfc_apply_interface_mapping_to_expr burnus at gcc dot gnu dot org
2008-11-01 14:44 ` janus at gcc dot gnu dot org
2008-11-01 14:51 ` janus at gcc dot gnu dot org
2008-11-01 15:00 ` janus at gcc dot gnu dot org
2008-11-01 15:04 ` janus at gcc dot gnu dot org
2008-11-01 19:08 ` janus at gcc dot gnu dot org
2008-11-01 20:15 ` dominiq at lps dot ens dot fr
2008-11-01 21:59 ` janus at gcc dot gnu dot org
2008-11-01 22:01 ` 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=bug-36426-13404@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: 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).