public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stefan.mauerberger at gmail dot com" <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: Tue, 22 Jan 2013 19:08:00 -0000	[thread overview]
Message-ID: <bug-56008-4-LCp8SmjgMK@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

--- Comment #7 from stefan.mauerberger at gmail dot com 2013-01-22 19:08:10 UTC ---
Unfortunately, I do not understand a thing about all the internals and the
actual implementations. I just wanted to let you know that I am totally
overwhelmed how series bugs are treated and how quick bug-fixes approach. You
guys are just awesome! 
In case I can support you in any kind fixing that bug, please let me know.


  parent reply	other threads:[~2013-01-22 19:08 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
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 [this message]
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-LCp8SmjgMK@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).