public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40440] Automatic deallocation component of DT function return value
Date: Thu, 18 Jun 2009 21:15:00 -0000 [thread overview]
Message-ID: <20090618211533.7065.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40440-15192@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from burnus at gcc dot gnu dot org 2009-06-18 21:15 -------
(In reply to comment #10)
> Yes, I understood after a bit of dyslexia about it :-(
>
> Since the function result is a pointer, it is an ultimate component and, I
> think, the deallocation of the allocatable components should not be attempted.
I agree that no deallocation should happen. (Sorry for claiming so before.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40440
next prev parent reply other threads:[~2009-06-18 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 21:50 [Bug fortran/40440] New: [4.5.0 Regression] Garbage or segmentation fault in allocatable array derived type structures juergen dot reuter at desy dot de
2009-06-14 22:14 ` [Bug fortran/40440] " kargl at gcc dot gnu dot org
2009-06-14 22:19 ` juergen dot reuter at desy dot de
2009-06-15 8:52 ` [Bug fortran/40440] [4.4/4.5 " burnus at gcc dot gnu dot org
2009-06-15 12:17 ` burnus at gcc dot gnu dot org
2009-06-15 13:09 ` [Bug fortran/40440] Automatic deallocation component of DT function return value burnus at gcc dot gnu dot org
2009-06-18 9:44 ` pault at gcc dot gnu dot org
2009-06-18 13:33 ` juergen dot reuter at desy dot de
2009-06-18 14:45 ` burnus at gcc dot gnu dot org
2009-06-18 15:18 ` burnus at gcc dot gnu dot org
2009-06-18 20:52 ` pault at gcc dot gnu dot org
2009-06-18 21:15 ` burnus at gcc dot gnu dot org [this message]
2009-06-19 0:20 ` pault at gcc dot gnu dot org
2009-06-19 21:58 ` pault at gcc dot gnu dot org
2009-07-09 19:28 ` pault at gcc dot gnu dot org
2009-07-09 19:29 ` pault at gcc dot gnu dot org
2009-10-11 12:20 ` pault at gcc dot gnu dot org
2009-10-11 12:26 ` pault at gcc dot gnu dot 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=20090618211533.7065.qmail@sourceware.org \
--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).