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/46783] New: [OOP] TRANSFER with polymorphic MOLD= Date: Fri, 03 Dec 2010 14:16:00 -0000 [thread overview] Message-ID: <bug-46783-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46783 Summary: [OOP] TRANSFER with polymorphic MOLD= Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: janus@gcc.gnu.org Cf. http://j3-fortran.org/pipermail/j3/2010-December/004026.html Currently, the declared type is used for MOLD= in TRANSFER. It seems as if the effective type should be used instead. This is a tracker bug as the standard is a bit ambiguous about it; I assume that there will be an IR (interpretation request) about it. Currently, F2008 just has: MOLD shall be a scalar or array of any type. If it is a variable, it need not be defined. Result Characteristics. The result is of the same type and type parameters as MOLD.
next reply other threads:[~2010-12-03 14:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-03 14:16 burnus at gcc dot gnu.org [this message] 2013-06-20 18:44 ` [Bug fortran/46783] " dominiq at lps dot ens.fr 2015-10-09 8:53 ` 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-46783-4@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).