From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR55854/PR55763 - CLASS(*) fixes
Date: Fri, 04 Jan 2013 05:00:00 -0000 [thread overview]
Message-ID: <CAGkQGiLh4auPLEaOg+U=HPn5TKRLShwvYVK5VoMPBYjL81JQnw@mail.gmail.com> (raw)
In-Reply-To: <50E5B41D.6010809@net-b.de>
Dear Tobias,
Hah! You are right about null(x). It is an odd constraint, though,
since all that is used is the type/kind information.
OK for trunk
Thanks for the patch.
Paul
On 3 January 2013 17:38, Tobias Burnus <burnus@net-b.de> wrote:
> The attached patch fixes two ICE.
>
> Regarding the unlimited_polymorphic_3.f03 change: "null(x)" is invalid as
> initialization expression (null-init). Using "ptr2 => x" would be valid, but
> it ICEs. (Cf. PR55763, comment 13)
>
> Build and regtested on x86-64-gnu-linux.
> OK for the trunk?
>
> Tobias
--
The knack of flying is learning how to throw yourself at the ground and miss.
--Hitchhikers Guide to the Galaxy
prev parent reply other threads:[~2013-01-04 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 16:39 Tobias Burnus
2013-01-04 5:00 ` Paul Richard Thomas [this message]
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='CAGkQGiLh4auPLEaOg+U=HPn5TKRLShwvYVK5VoMPBYjL81JQnw@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--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).