public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54286] [4.8 Regression] Accepts invalid proc-pointer assignments involving proc-ptr function result Date: Wed, 19 Sep 2012 12:29:00 -0000 [thread overview] Message-ID: <bug-54286-4-hyiGOuJzMb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54286-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54286 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid CC| |burnus at gcc dot gnu.org --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-09-19 12:28:50 UTC --- (When you look into this problem: I think the current handling of assumed-rank is also wrong (sorry, my mistake). For array passing, assumed-rank dummies take any rank (including scalar). However, for dummy procedures or proc-pointers, if the dummy/proc-pointer has an assumed rank dummy, the actual/proc/target has to have one too.)
next prev parent reply other threads:[~2012-09-19 12:29 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-16 15:05 [Bug fortran/54286] New: " janus at gcc dot gnu.org 2012-09-19 12:07 ` [Bug fortran/54286] " rguenth at gcc dot gnu.org 2012-09-19 12:29 ` burnus at gcc dot gnu.org [this message] 2013-01-08 21:44 ` pault at gcc dot gnu.org 2013-01-09 9:44 ` pault at gcc dot gnu.org 2013-01-09 12:07 ` mikael at gcc dot gnu.org 2013-01-09 13:08 ` pault at gcc dot gnu.org 2013-01-13 8:58 ` pault at gcc dot gnu.org 2013-01-14 5:53 ` pault at gcc dot gnu.org 2013-01-14 20:32 ` pault at gcc dot gnu.org 2013-01-14 22:35 ` dominiq at lps dot ens.fr 2013-01-15 5:29 ` pault at gcc dot gnu.org 2013-01-15 5:34 ` pault at gcc dot gnu.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-54286-4-hyiGOuJzMb@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).