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 fortran/42693] Missing gcc-internal-format on messages from gfc_arith_error
Date: Mon, 22 Jun 2020 10:47:06 +0000 [thread overview]
Message-ID: <bug-42693-4-uliIPrV5wE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42693-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42693
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Mark Eggleston
<markeggleston@gcc.gnu.org>:
https://gcc.gnu.org/g:d57bf2315e024ada3393ad967e8f632121383c9c
commit r11-1583-gd57bf2315e024ada3393ad967e8f632121383c9c
Author: Mark Eggleston <markeggleston@gcc.gnu.org>
Date: Wed Jun 10 11:41:56 2020 +0100
Fortran : Missing gcc-internal-format PR42693
Messages in gfc_arith_error contain gcc internal format specifiers
which should be enclosed in G_() in order to be correctly translated.
2020-06-22 Mark Eggleston <markeggleston@gcc.gnu.org>
gcc/fortran/
PR fortran/42693
* arith.c (gfc_arith_error): Enclose strings in G_() instead
of _().
next prev parent reply other threads:[~2020-06-22 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42693-4@http.gcc.gnu.org/bugzilla/>
2012-01-24 11:11 ` dominiq at lps dot ens.fr
2012-02-16 14:36 ` burnus at gcc dot gnu.org
2020-06-01 13:31 ` markeggleston at gcc dot gnu.org
2020-06-06 12:55 ` goeran at uddeborg dot se
2020-06-22 10:47 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-23 6:29 ` markeggleston at gcc dot gnu.org
2010-01-11 21:00 [Bug fortran/42693] New: " goeran at uddeborg dot se
2010-01-11 22:29 ` [Bug fortran/42693] " burnus at gcc dot gnu dot 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-42693-4-uliIPrV5wE@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).