public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Cc: rep.dot.nop@gmail.com, Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Subject: PING Re: [PATCH] Fortran: Remove double spaces in open() warning [PR99884]
Date: Mon, 14 Nov 2022 10:09:01 +0100	[thread overview]
Message-ID: <20221114100901.6acb9e25@nbbrfq> (raw)
In-Reply-To: <20211031125746.2032831-1-rep.dot.nop@gmail.com>

yearly ping. Ok for trunk after re-regtesting?

thanks,

On Sun, 31 Oct 2021 13:57:46 +0100
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> wrote:

> From: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
> 
> gcc/fortran/ChangeLog:
> 
> 	PR fortran/99884
> 	* io.c (check_open_constraints): Remove double spaces.
> ---
>  gcc/fortran/io.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gcc/fortran/io.c b/gcc/fortran/io.c
> index fc97df79eca..9506f35008e 100644
> --- a/gcc/fortran/io.c
> +++ b/gcc/fortran/io.c
> @@ -2513,7 +2513,7 @@ check_open_constraints (gfc_open *open, locus *where)
>  	  spec = "";
>  	}
>  
> -      warn_or_error (G_("%s specifier at %L not allowed in OPEN statement for "
> +      warn_or_error (G_("%sspecifier at %L not allowed in OPEN statement for "
>  		     "unformatted I/O"), spec, loc);
>      }
>  


  reply	other threads:[~2022-11-14  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 12:57 Bernhard Reutner-Fischer
2022-11-14  9:09 ` Bernhard Reutner-Fischer [this message]
2022-11-14  9:44   ` PING " Richard Biener

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=20221114100901.6acb9e25@nbbrfq \
    --to=rep.dot.nop@gmail.com \
    --cc=aldot@gcc.gnu.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).