public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56008] [F03] wrong code with lhs-realloc on assignment with derived types having allocatable components
Date: Sat, 19 Jan 2013 15:55:00 -0000 [thread overview]
Message-ID: <bug-56008-4-XcPgak1JWR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56008-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56008
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot |pault at gcc dot gnu.org
|gnu.org |
--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> 2013-01-19 15:54:50 UTC ---
Created attachment 29221
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29221
Fix for this PR and PR 47517
Bootstraps and regtests OK
The data pointers of allocatable components need to be nullified, after
(re)allocation, before the assignment starts because of the test in allocation
for the allocation status of these components.
It's nearly 'obvious' but took me an age to get it :-)
I'll submit properly once I am back in France (tomorrow night if snow allows).
Paul
next prev parent reply other threads:[~2013-01-19 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 19:37 [Bug fortran/56008] New: [F03] lhs-allocation invoking the array-constructor on DDTs causes memory error stefan.mauerberger at gmail dot com
2013-01-16 19:38 ` [Bug fortran/56008] " stefan.mauerberger at gmail dot com
2013-01-16 19:39 ` stefan.mauerberger at gmail dot com
2013-01-16 22:51 ` [Bug fortran/56008] [F03] wrong code with lhs-realloc on assignment with derived types having allocatable components burnus at gcc dot gnu.org
2013-01-19 15:55 ` pault at gcc dot gnu.org [this message]
2013-01-20 13:35 ` dominiq at lps dot ens.fr
2013-01-21 19:30 ` pault at gcc dot gnu.org
2013-01-22 19:08 ` stefan.mauerberger at gmail dot com
2013-02-04 22:33 ` pault at gcc dot gnu.org
2013-02-04 22:36 ` pault at gcc dot gnu.org
2013-02-10 18:35 ` stefan.mauerberger at gmail dot com
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-56008-4-XcPgak1JWR@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: 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).