From: Tobias Burnus <burnus@net-b.de>
To: fortran@gcc.gnu.org
Cc: gcc patches <gcc-patches@gcc.gnu.org>,
Thomas Koenig <tkoenig@netcologne.de>
Subject: Re: [patch, Fortran] Fix PR 53824
Date: Sun, 15 Jul 2012 19:44:00 -0000 [thread overview]
Message-ID: <50031D79.3040307@net-b.de> (raw)
In-Reply-To: <5002A8DA.60704@netcologne.de>
Thomas Koenig wrote:
> this fixes an ICE with allocation of coarrays. Regression-tested.
> OK for trunk? What about 4.7?
OK. Thanks for the patch. Regarding 4.7, I don't have a strong opinion.
Given that it is a simple patch and given that (single-image) coarrays
work rather well in 4.7, maybe one should.
Tobias
> 2012-07-15 Thomas König <tkoenig@gcc.gnu.org>
>
> PR fortran/53824
> * resolve.c (resolve_allocate_deallocate): If both
> start indices are NULL, skip the test for equality.
>
> 2012-07-15 Thomas König <tkoenig@gcc.gnu.org>
>
> PR fortran/53824
> * gfortran.dg/coarray_allocate_1.f90: New test.
prev parent reply other threads:[~2012-07-15 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 11:26 Thomas Koenig
2012-07-15 19:44 ` Tobias Burnus [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=50031D79.3040307@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).