public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/24558] ENTRY doesn't work in module procedures Date: Tue, 30 May 2006 07:43:00 -0000 [thread overview] Message-ID: <20060530074316.25773.qmail@sourceware.org> (raw) In-Reply-To: <bug-24558-11549@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from pault at gcc dot gnu dot org 2006-05-30 07:43 ------- Created an attachment (id=11535) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11535&action=view) Preliminary patch to fix the PR This needs a lot of sprucing up and checking out but it compiles and runs the version below of your testcase. The disgnostic gfc_warning_now's need removing too! Paul module foo contains function n1(a) integer :: n1, n2, a, b integer, save :: c c = a n1 = c**3 return entry n2(b) n2 = c * b n2 = n2**2 return end function n1 function n3(d) integer :: n3, d n3 = n2(d)*n1(d) return end function n3 end module foo program bar use foo print *, n1(9) print *, n2(2) print *, n3(19) end program bar -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24558
next prev parent reply other threads:[~2006-05-30 7:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-27 12:40 [Bug fortran/24558] New: " eedelman at gcc dot gnu dot org 2005-10-27 23:12 ` [Bug fortran/24558] " pinskia at gcc dot gnu dot org 2006-03-14 15:14 ` pinskia at gcc dot gnu dot org 2006-03-15 8:15 ` pault at gcc dot gnu dot org 2006-05-30 7:43 ` pault at gcc dot gnu dot org [this message] 2006-05-31 12:45 ` patchapp at dberlin dot org 2006-06-09 22:16 ` pault at gcc dot gnu dot org 2006-06-11 22:33 ` pault at gcc dot gnu dot org 2006-06-11 22:34 ` pault 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=20060530074316.25773.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).