public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sfilippone at uniroma2 dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46174] [OOP] ALLOCATE with SOURCE: Deep copy missing
Date: Tue, 26 Oct 2010 07:10:00 -0000 [thread overview]
Message-ID: <20101026071000.j1qPhPp72NLl9WUAHyzLjlBHRiBjsleWhZffKsMN8GI@z> (raw)
In-Reply-To: <bug-46174-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46174
Salvatore Filippone <sfilippone at uniroma2 dot it> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sfilippone at uniroma2 dot
| |it
--- Comment #1 from Salvatore Filippone <sfilippone at uniroma2 dot it> 2010-10-26 07:09:41 UTC ---
(In reply to comment #0)
> The following is in a sense a follow up to PR 45451.
>
> Assuming that X and Y are both polymorphic (CLASS) and the following operation:
> ALLOCATE (x, SOURCE=y)
> or
> x = y ! Fortran 2008: (Re)alloc on assignment with polymorphic LHS
>
What about MOLD= for polymorphic variables?
next prev parent reply other threads:[~2010-10-26 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 21:45 [Bug fortran/46174] New: " burnus at gcc dot gnu.org
2010-10-26 7:10 ` sfilippone at uniroma2 dot it [this message]
2010-10-26 7:44 ` [Bug fortran/46174] " burnus at gcc dot gnu.org
2010-10-26 13:27 ` burnus at gcc dot gnu.org
2010-10-26 19:00 ` domob at gcc dot gnu.org
2010-11-03 9:18 ` burnus at gcc dot gnu.org
2010-11-05 9:48 ` janus at gcc dot gnu.org
2010-11-05 18:15 ` janus at gcc dot gnu.org
2010-11-05 18:39 ` janus 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=20101026071000.j1qPhPp72NLl9WUAHyzLjlBHRiBjsleWhZffKsMN8GI@z \
--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: link
Be 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).