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/105456] Child I/O does not propage iostat Date: Sun, 25 Feb 2024 22:55:39 +0000 [thread overview] Message-ID: <bug-105456-4-l1fQUY24eJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105456-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105456 --- Comment #5 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:3f58f96a4e8255e222953f9856bcd6c25f7b33cd commit r14-9168-g3f58f96a4e8255e222953f9856bcd6c25f7b33cd Author: Jerry DeLisle <jvdelisle@gcc.gnu.org> Date: Sun Feb 25 14:50:07 2024 -0800 libgfortran: Propagate user defined iostat and iomsg. PR libfortran/105456 libgfortran/ChangeLog: * io/list_read.c (list_formatted_read_scalar): Add checks for the case where a user defines their own error codes and error messages and generate the runtime error. * io/transfer.c (st_read_done): Whitespace. gcc/testsuite/ChangeLog: * gfortran.dg/pr105456.f90: New test.
next prev parent reply other threads:[~2024-02-25 22:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-02 16:49 [Bug libfortran/105456] New: " tkoenig at gcc dot gnu.org 2022-05-02 16:50 ` [Bug libfortran/105456] " tkoenig at gcc dot gnu.org 2023-04-26 6:56 ` rguenth at gcc dot gnu.org 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2023-08-15 3:10 ` jvdelisle at gcc dot gnu.org 2024-02-22 19:13 ` jvdelisle at gcc dot gnu.org 2024-02-25 22:55 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-06 4:54 ` cvs-commit at gcc dot gnu.org 2024-03-07 3:58 ` cvs-commit at gcc dot gnu.org 2024-03-12 1:08 ` 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-105456-4-l1fQUY24eJ@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).