public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/107068] Run-time error when reading logical arrays with a namelist
Date: Wed, 28 Sep 2022 18:23:32 +0000 [thread overview]
Message-ID: <bug-107068-4-xoqqFLpSqH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107068-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107068
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Component|fortran |libfortran
Last reconfirmed| |2022-09-28
--- Comment #2 from anlauf at gcc dot gnu.org ---
Confirmed.
Renaming the second variable (e.g. flp -> xlp) works around the problem,
as well as interchanging the lines in the namelist input.
It appears that while scanning the namelist input we first see the T,
then F, for which we try to determine if it means .false. or is part of
a variable name, and then possibly screw up because we see a comma when
referring to an element of rank-2 array flp.
There is also no error when using a rank-1 array for flp and referring
to flp(2) etc.
next prev parent reply other threads:[~2022-09-28 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 13:16 [Bug fortran/107068] New: " r.m.potvliege at durham dot ac.uk
2022-09-28 13:28 ` [Bug fortran/107068] " r.m.potvliege at durham dot ac.uk
2022-09-28 18:23 ` anlauf at gcc dot gnu.org [this message]
2022-09-28 20:25 ` [Bug libfortran/107068] " r.m.potvliege at durham dot ac.uk
2022-09-28 20:26 ` r.m.potvliege at durham dot ac.uk
2023-05-13 19:44 ` jvdelisle at gcc dot gnu.org
2023-05-14 1:30 ` jvdelisle at gcc dot gnu.org
2023-05-14 3:34 ` jvdelisle at gcc dot gnu.org
2024-02-17 0:26 ` jvdelisle at gcc dot gnu.org
2024-02-17 15:35 ` cvs-commit at gcc dot gnu.org
2024-04-10 2:31 ` jvdelisle at gcc dot gnu.org
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=bug-107068-4-xoqqFLpSqH@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).