From: Thomas Koenig <tkoenig@netcologne.de>
To: Jakub Jelinek <jakub@redhat.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: Tobias Burnus <tobias@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [PATCH] fortran: Fix up initializers of param(0) PARAMETERs [PR103691]
Date: Sat, 26 Mar 2022 12:27:59 +0100 [thread overview]
Message-ID: <a574c183-3f86-c41e-8ab2-122c0c1baaf6@netcologne.de> (raw)
In-Reply-To: <Yj2owTg/uEFnlUKO@tucnak>
On 25.03.22 12:34, Jakub Jelinek via Fortran wrote:
> What is the behavior with a RANGE_EXPR when one has { [0..10] = ++i;
> }, is that applying the side-effects 11 times or once ?
For side effects during the evaluation of expression, Fortran has a
clear "if you depend on it, it's your fault" rule. In F 2018, it says
10.1.7 Evaluation of operands
1 It is not necessary for a processor to evaluate all of the operands of
an expression, or to evaluate entirely each operand, if the value of the
expression can be determined otherwise.
Also, the semantics of
a(a:b) = expr
say that the expression on the LHS is evaluated only once before
assignment. So, anything that looks like that should be translated
to
tmp = ++i;
[0..10] = tmp;
next prev parent reply other threads:[~2022-03-26 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 8:57 Jakub Jelinek
2022-03-25 10:13 ` Tobias Burnus
2022-03-25 11:16 ` Richard Biener
2022-03-25 11:34 ` Jakub Jelinek
2022-03-25 12:13 ` Richard Biener
2022-03-25 12:15 ` Jakub Jelinek
2022-03-26 11:27 ` Thomas Koenig [this message]
2022-03-26 17:13 ` Richard Biener
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=a574c183-3f86-c41e-8ab2-122c0c1baaf6@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
--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).