From: jerry DeLisle <jvdelisle@charter.net>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 49324: Deep copy array constr of DT with allocatable components
Date: Fri, 10 Jun 2011 17:45:00 -0000 [thread overview]
Message-ID: <4DF2565E.9020801@charter.net> (raw)
In-Reply-To: <4DF20A1D.2000709@net-b.de>
On 06/10/2011 05:12 AM, Tobias Burnus wrote:
> This patch fixes parts of the PR 49324: There was a deep copy missing for
> assigning an array constructor of a DT with allocatable components.
>
> Whether a deep copy is done, depends on a flag. I think the flag has been added
> to avoid a deep copy and multiple evaluation for functions, which return DT w/
> allocatable components, and for user-defined operators.
>
> Remains to do be done:
> - RESHAPE is mishandled (design error): No deep copy.
> - Reallocate on assignment fails (missing NULL initialization of the malloced
> memory).
>
> Build and regtested on x86-64-linux. OK?
>
> Tobias
OK, thanks for patch.
Jerry
prev parent reply other threads:[~2011-06-10 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 12:18 Tobias Burnus
2011-06-10 17:45 ` jerry DeLisle [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=4DF2565E.9020801@charter.net \
--to=jvdelisle@charter.net \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).