public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/113223] NAMELIST internal write missing leading blank character Date: Thu, 04 Jan 2024 16:57:08 +0000 [thread overview] Message-ID: <bug-113223-4-ilYK4iNfHw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113223-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113223 --- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Created attachment 56990 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56990&action=edit Suggested patch including affected test cases Regression tested OK. Three test cases affected. $ git status On branch master Your branch is up to date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: gcc/testsuite/gfortran.dg/dtio_25.f90 modified: gcc/testsuite/gfortran.dg/namelist_57.f90 modified: gcc/testsuite/gfortran.dg/namelist_65.f90 modified: libgfortran/io/write.c no changes added to commit (use "git add" and/or "git commit -a") This looks good to me and I will commit as simple and obvious.
next prev parent reply other threads:[~2024-01-04 16:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-03 19:51 [Bug libfortran/113223] New: " kargl at gcc dot gnu.org 2024-01-03 19:51 ` [Bug libfortran/113223] " kargl at gcc dot gnu.org 2024-01-03 21:56 ` kargl at gcc dot gnu.org 2024-01-03 22:06 ` jvdelisle at gcc dot gnu.org 2024-01-04 16:57 ` jvdelisle at gcc dot gnu.org [this message] 2024-01-04 18:31 ` kargl at gcc dot gnu.org 2024-01-07 18:32 ` cvs-commit at gcc dot gnu.org 2024-01-13 21:02 ` cvs-commit at gcc dot gnu.org 2024-01-13 21:04 ` 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-113223-4-ilYK4iNfHw@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).