public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Sat, 17 Feb 2024 15:35:22 +0000 [thread overview] Message-ID: <bug-107068-4-TPTR2piJUQ@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 --- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jerry DeLisle <jvdelisle@gcc.gnu.org>: https://gcc.gnu.org/g:fccfe6625121512f247cb59888e50eb9dcc84409 commit r14-9048-gfccfe6625121512f247cb59888e50eb9dcc84409 Author: Jerry DeLisle <jvdelisle@gcc.gnu.org> Date: Fri Feb 16 17:06:37 2024 -0800 libgfortran: Fix namelist read. PR libfortran/107068 libgfortran/ChangeLog: * io/list_read.c (read_logical): When looking for a possible variable name, check for left paren, indicating a possible array reference. gcc/testsuite/ChangeLog: * gfortran.dg/pr107068.f90: New test.
next prev parent reply other threads:[~2024-02-17 15:35 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 ` [Bug libfortran/107068] " anlauf at gcc dot gnu.org 2022-09-28 20:25 ` 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 [this message] 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-TPTR2piJUQ@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: linkBe 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).