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 fortran/114611] H edit descriptor should flag as error with -std-f95 (or higher)
Date: Sun, 07 Apr 2024 18:43:21 +0000	[thread overview]
Message-ID: <bug-114611-4-BVjhLh1pis@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114611-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114611

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
                 CC|                            |jvdelisle at gcc dot gnu.org
   Last reconfirmed|                            |2024-04-07

--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Here is a fix. It wiggles on about 5 test cases that will need to be adjusted.

diff --git a/gcc/fortran/io.cc b/gcc/fortran/io.cc
index 6fd69f7c9a8..e6a5144b028 100644
--- a/gcc/fortran/io.cc
+++ b/gcc/fortran/io.cc
@@ -1129,12 +1129,10 @@ data_desc:
       break;

     case FMT_H:
-      if (!(gfc_option.allow_std & GFC_STD_GNU) && !inhibit_warnings)
+      if (!gfc_notify_std (GFC_STD_F95_DEL, "H format specifier at %C"))
        {
          if (mode != MODE_FORMAT)
            format_locus.nextc += format_string_pos;
-         gfc_warning (0, "The H format specifier at %L is"
-                      " a Fortran 95 deleted feature", &format_locus);
        }
       if (mode == MODE_STRING)
        {

      reply	other threads:[~2024-04-07 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 19:19 [Bug fortran/114611] New: " w6ws at earthlink dot net
2024-04-07 18:43 ` jvdelisle at gcc dot gnu.org [this message]

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-114611-4-BVjhLh1pis@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).