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/56808] Coarray: Wrongly accepts coindexed arguments to INTENT(OUT) dummies Date: Tue, 02 Apr 2013 08:07:00 -0000 [thread overview] Message-ID: <bug-56808-4-5GoN6ELgMa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56808-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56808 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-04-02 08:06:54 UTC --- Actually, that example is probably okay. Steven Lionel wrote: "But reading this I wonder if it's intended to mean actual arguments of derived type with allocatable components, rather than a regular allocatable array, since there's no issue of making copies of subcomponents here. Let me discuss it with my team here." However, the following code should be invalid (due to the implicit deallocating the allocatable component *on the remote image*): type t integer, allocatable :: x end type t class(t), allocatable :: x[:] call bar(x[1]) ! <<< Wrongly accepted. ! call foo(x[1]) ! OK: Rejected coindexed polymorphic -> polymorphic not allowed contains subroutine bar(r) type(t) :: r end subroutine foo(r) class(t) :: r end end
next prev parent reply other threads:[~2013-04-02 8:07 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-02 8:02 [Bug fortran/56808] New: " burnus at gcc dot gnu.org 2013-04-02 8:07 ` burnus at gcc dot gnu.org [this message] 2015-10-20 17:05 ` [Bug fortran/56808] " dominiq at lps dot ens.fr
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-56808-4-5GoN6ELgMa@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).