From: Harald Anlauf <anlauf@gmx.de>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR fortran/99205 - [10/11 Regression] Out of memory with undefined character length
Date: Wed, 10 Mar 2021 20:43:25 +0100 [thread overview]
Message-ID: <trinity-982a86be-17e0-42a2-ad3c-b00a5cf85014-1615405404985@3c-app-gmx-bs58> (raw)
In-Reply-To: <8a63eb89-91e6-1e8d-870e-8a2f7a6750df@codesourcery.com>
Dear Tobias,
thanks for your comments.
> > A variable that is a data statement object shall be a designator,
> > thus a character variable shall have a constant length.
>
> This comment is wrong: A designator does not imply this – nor is
> F2018:C875 violated, not even the substring starting/ending point
> const expr bit.
OK, I will think of a better wording.
> In the following variant of the program, the invalid
> variable declaration of 'c' itself is avoided by using
> a block:
>
> integer :: ll
> ll = 4
> block
> character(ll) :: c(2), cc(2)
> character(ll) :: c2(2), cc2(2)
> data c /'a', 'b'/
> data c2(:)(1:1) /'a', 'b'/
> common /block/ cc, cc2
> end block
> end
No, this example is invalid, see
C1107(R1107) A block-specification-part shall not contain a COMMON, EQUIVALENCE, INTENT, NAMELIST,
OPTIONAL, statement function, or VALUE statement.
Harald
next prev parent reply other threads:[~2021-03-10 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 19:45 Harald Anlauf
2021-03-10 10:06 ` Tobias Burnus
2021-03-10 19:43 ` Harald Anlauf [this message]
2021-03-10 20:18 ` Tobias Burnus
2021-03-10 21:26 ` Harald Anlauf
2021-03-10 21:52 ` 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=trinity-982a86be-17e0-42a2-ad3c-b00a5cf85014-1615405404985@3c-app-gmx-bs58 \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/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).