public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "erik dot edelmann at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24426] gfortran ICE for valid derived type definition with default initialization
Date: Fri, 21 Oct 2005 12:03:00 -0000	[thread overview]
Message-ID: <20051021120302.3929.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24426-11543@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from erik dot edelmann at iki dot fi  2005-10-21 12:03 -------
(In reply to comment #0)
> It reminds me a bit of bug 16606 but is different as the compiler crashes.

It's indeed basically the same problem as in PR 16606; we assign a default
initializer to variables of derived types even when they are pointers.  The
only difference between this and PR 16606 is that that was for independent
variables, and this is for type components.  I'll think I can write a patch
today or tomorrow.


-- 

erik dot edelmann at iki dot fi changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erik dot edelmann at iki dot
                   |                            |fi


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24426


  parent reply	other threads:[~2005-10-21 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 11:03 [Bug fortran/24426] New: " sven dot buijssen at math dot uni-dortmund dot de
2005-10-18 13:42 ` [Bug fortran/24426] " pinskia at gcc dot gnu dot org
2005-10-18 13:46 ` pinskia at gcc dot gnu dot org
2005-10-21 12:03 ` erik dot edelmann at iki dot fi [this message]
2005-10-21 14:57 ` erik dot edelmann at iki dot fi
2005-10-22 17:02 ` cvs-commit at gcc dot gnu dot org
2005-10-22 17:09 ` cvs-commit at gcc dot gnu dot org
2005-10-22 21:22 ` pinskia 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=20051021120302.3929.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).