From: Jerry DeLisle <jvdelisle@charter.net>
To: Andre Vehreschild <vehre@gmx.de>,
GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
GCC-Fortran-ML <fortran@gcc.gnu.org>
Subject: Re: [Fortran, Patch, pr67538, v1] ICE with invalid source allocation
Date: Sun, 03 Apr 2016 19:23:00 -0000 [thread overview]
Message-ID: <57016D9C.9030402@charter.net> (raw)
In-Reply-To: <20160403181326.16103d56@vepi2>
On 04/03/2016 09:13 AM, Andre Vehreschild wrote:
> Hi all,
>
> the attached patch checks that for F2008-style allocate(arr1, source=s)
> the expression in s is array valued, when arr1 has no array spec and
> emits an error message saying:
>
> Array specification or array-valued SOURCE= expression required in ALLOCATE statement at (1)
>
> This fixes the ICE.
>
> Bootstrapped and regtests ok on x86_64-linux-gnu/F23. Ok for trunk?
>
> Regards,
> Andre
>
Yes, OK, thanks for patches.
Jerry
next prev parent reply other threads:[~2016-04-03 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 16:13 Andre Vehreschild
2016-04-03 19:23 ` Jerry DeLisle [this message]
2016-04-04 10:33 ` Andre Vehreschild
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=57016D9C.9030402@charter.net \
--to=jvdelisle@charter.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=vehre@gmx.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).