From: Janus Weil <janus@gcc.gnu.org>
To: Tobias Burnus <burnus@net-b.de>
Cc: gfortran <fortran@gcc.gnu.org>, gcc patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, OOP] PR 57306: ICE on valid with class pointer initialization
Date: Fri, 02 Aug 2013 09:01:00 -0000 [thread overview]
Message-ID: <CAKwh3qgfbTBT+TppVJ6QHBecFRTHqUBmmXwP61ZnciEfP-QZdw@mail.gmail.com> (raw)
In-Reply-To: <CAKwh3qh9KiNY6BF99m_cy=x=MQZrN_X0p+1idJ=rKSfB=1rhaw@mail.gmail.com>
ping!
2013/7/30 Janus Weil <janus@gcc.gnu.org>:
>> The attached update fixes it, and thus should hopefully be
>> regression-free. It also renames 'gfc_class_null_initializer' to
>> 'gfc_class_initializer', since it now also does other initializations
>> beside EXPR_NULL.
>>
>> Will do another regtest to make sure it's clean.
>
> No failures observed. As a test case I'm using now Tobias' extended
> version (attached). New ChangeLog below.
>
> Ok for trunk?
>
> Cheers,
> Janus
>
>
> 2013-07-30 Janus Weil <janus@gcc.gnu.org>
>
> PR fortran/57306
> * class.c (gfc_class_null_initializer): Rename to
> 'gfc_class_initializer'. Treat non-NULL init-exprs.
> * gfortran.h (gfc_class_null_initializer): Update prototype.
> * trans-decl.c (gfc_get_symbol_decl): Treat class pointers.
> * trans-expr.c (gfc_conv_initializer): Ditto.
> (gfc_trans_subcomponent_assign): Renamed gfc_class_null_initializer.
>
> 2013-07-30 Janus Weil <janus@gcc.gnu.org>
>
> PR fortran/57306
> * gfortran.dg/pointer_init_8.f90: New.
next prev parent reply other threads:[~2013-08-02 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 21:13 Janus Weil
2013-07-27 9:51 ` Tobias Burnus
2013-07-29 21:20 ` Janus Weil
2013-07-29 23:04 ` Janus Weil
2013-07-29 23:53 ` Janus Weil
2013-07-30 9:11 ` Janus Weil
2013-08-02 9:01 ` Janus Weil [this message]
2013-08-04 21:13 ` Tobias Burnus
2013-08-04 22:13 ` Janus Weil
2013-08-05 9:16 ` Janus Weil
2013-08-05 22:12 ` Tobias Burnus
2013-08-06 7:40 ` Janus Weil
2013-08-06 8:22 ` Janus Weil
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=CAKwh3qgfbTBT+TppVJ6QHBecFRTHqUBmmXwP61ZnciEfP-QZdw@mail.gmail.com \
--to=janus@gcc.gnu.org \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).