public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Eggleston <mark.eggleston@codethink.co.uk>
To: Thomas Koenig <tkoenig@netcologne.de>, sgk@troutmask.apl.washington.edu
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH] fortran: ICE using undeclared symbol in array constructor, PR93484
Date: Mon, 24 Feb 2020 14:50:00 -0000	[thread overview]
Message-ID: <bd9e0e27-e2f1-ef3f-1839-23f8415fd7af@codethink.co.uk> (raw)
In-Reply-To: <37db0f3c-6f16-1bc2-9311-e52cfe150497@netcologne.de>


On 24/02/2020 14:34, Thomas Koenig wrote:
> Hi Mark,
>
>>> Might need
>>>
>>>          gfc_reduce_init_expr (e);
>>>
>>> here.  The kind type parameter should be a constant expression.
>>
>> Not needed. I've also checked use of the kind argument, it is 
>> evidently checked elsewhere: if k is allowed to be implicitly 
>> declared and is used as the kind argument errors are reported that it 
>> is not a constant, if implicit declaration is not allowed a "has no 
>> IMPLICIT type" error is produced.
>
> Is there a test case that covers this already?  OK if such a test
> case exists, also OK with such a test case (or if looking for it
> is too bother :-)

I've had a quick look and there doesn't appear to be a test for using a 
non-constant for kind arguments. I think a proper set of tests for 
invalid kind arguments that covers declarations and intrinsic arguments 
should be added that is separate from this patch.  Should that be done 
while we're in stage 4 or should it wait for stage 1?

In the meantime I'll commit this patch either today or tomorrow.

>
> Regards
>
>     Thomas
>
-- 
https://www.codethink.co.uk/privacy.html

  reply	other threads:[~2020-02-24 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 12:10 Mark Eggleston
2020-02-11 15:23 ` Steve Kargl
2020-02-24 14:19   ` Mark Eggleston
2020-02-24 14:34     ` Thomas Koenig
2020-02-24 14:50       ` Mark Eggleston [this message]
2020-02-24 15:01         ` Tobias Burnus

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=bd9e0e27-e2f1-ef3f-1839-23f8415fd7af@codethink.co.uk \
    --to=mark.eggleston@codethink.co.uk \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    --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).