public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58652] ICE with move_alloc and unlimited polymorphic
Date: Wed, 16 Oct 2013 20:46:00 -0000	[thread overview]
Message-ID: <bug-58652-4-qrmMzslm2B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58652-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Wed Oct 16 20:46:33 2013
New Revision: 203720

URL: http://gcc.gnu.org/viewcvs?rev=203720&root=gcc&view=rev
Log:
2013-10-16  Tobias Burnus  <burnus@net-b.de>

        PR fortran/58652
        * interface.c (compare_parameter): Accept passing CLASS(*)
        to CLASS(*).

2013-10-16  Tobias Burnus  <burnus@net-b.de>

        PR fortran/58652
        * gfortran.dg/unlimited_polymorphic_12.f90: New.


Added:
    trunk/gcc/testsuite/gfortran.dg/unlimited_polymorphic_12.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/interface.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2013-10-16 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 22:26 [Bug fortran/58652] New: " vladimir.fuka at gmail dot com
2013-10-07  7:52 ` [Bug fortran/58652] " burnus at gcc dot gnu.org
2013-10-14 21:26 ` burnus at gcc dot gnu.org
2013-10-15  6:14 ` burnus at gcc dot gnu.org
2013-10-15  6:20 ` burnus at gcc dot gnu.org
2013-10-15  6:24 ` burnus at gcc dot gnu.org
2013-10-16 20:46 ` burnus at gcc dot gnu.org [this message]
2013-10-16 20:48 ` burnus at gcc dot gnu.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=bug-58652-4-qrmMzslm2B@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).