public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60507] Passing function call into procedure argument not caught Date: Fri, 02 Jan 2015 11:25:00 -0000 [thread overview] Message-ID: <bug-60507-4-hZpB5tzFSZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60507-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60507 --- Comment #7 from janus at gcc dot gnu.org --- Author: janus Date: Fri Jan 2 11:24:32 2015 New Revision: 219141 URL: https://gcc.gnu.org/viewcvs?rev=219141&root=gcc&view=rev Log: 2015-01-02 Janus Weil <janus@gcc.gnu.org> PR fortran/60507 * interface.c (is_procptr_result): New function to check if an expression is a procedure-pointer result. (compare_actual_formal): Use it. 2015-01-02 Janus Weil <janus@gcc.gnu.org> PR fortran/60507 * gfortran.dg/dummy_procedure_11: New. Added: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/ChangeLog-2014 - copied unchanged from r219140, trunk/gcc/fortran/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/ChangeLog-2014 - copied unchanged from r219140, trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/dummy_procedure_11.f90 Modified: trunk/gcc/fortran/interface.c
prev parent reply other threads:[~2015-01-02 11:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-12 8:52 [Bug fortran/60507] New: Passing real expression " vladimir.fuka at gmail dot com 2014-03-12 13:47 ` [Bug fortran/60507] " janus at gcc dot gnu.org 2014-03-12 16:46 ` [Bug fortran/60507] Passing function call " janus at gcc dot gnu.org 2014-03-13 20:12 ` janus at gcc dot gnu.org 2014-03-18 15:33 ` janus at gcc dot gnu.org 2014-12-26 13:42 ` dominiq at lps dot ens.fr 2014-12-29 12:12 ` janus at gcc dot gnu.org 2015-01-02 11:25 ` janus at gcc dot gnu.org [this message]
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-60507-4-hZpB5tzFSZ@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: 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).