From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR57549 - fix type-spec handling with array constructors
Date: Fri, 07 Jun 2013 14:50:00 -0000 [thread overview]
Message-ID: <20130607145014.GA98085@troutmask.apl.washington.edu> (raw)
In-Reply-To: <51B1E848.1040302@net-b.de>
On Fri, Jun 07, 2013 at 04:03:52PM +0200, Tobias Burnus wrote:
> Unreviewed patches:
> * http://gcc.gnu.org/ml/fortran/2013-06/msg00027.html
> * http://gcc.gnu.org/ml/fortran/2013-06/msg00048.html
>
> * * *
>
> As with ALLOCATE (type-spec :: ...), also array constructors take as
> type-spec a type name ("integer, my_dt, etc.) without an extra TYPE().
>
> Thus, instead of using the decl.c var decl function, we use the same as
> for allocate.
>
> Build and regtested on x86-64-gnu-linux.
> OK for the trunk?
>
OK. Thanks for the patch.
--
Steve
prev parent reply other threads:[~2013-06-07 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 14:03 Tobias Burnus
2013-06-07 14:50 ` Steve Kargl [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=20130607145014.GA98085@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).