public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52279] Fortran translation issues
Date: Wed, 01 Jul 2020 21:39:44 +0000 [thread overview]
Message-ID: <bug-52279-4-qRvlTnAAIc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52279-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52279
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to CVS Commits from comment #1)
> The master branch has been updated by Mark Eggleston
> <markeggleston@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:0a7183f6d173cbd69025a3deb30d16f91e6392b2
>
> commit r11-1764-g0a7183f6d173cbd69025a3deb30d16f91e6392b2
> Author: Mark Eggleston <markeggleston@gcc.gnu.org>
> Date: Tue Jun 2 08:38:01 2020 +0100
>
> Fortran : Fortran translation issues PR52279
>
> Mark strings for translation by enclosing in G_() and _().
>
> 2020-06-24 Mark Eggleston <markeggleston@gcc.gnu.org>
>
> gcc/fortran/
>
> PR fortran/52279
> * arith.c (reduce_binary_aa): Mark for translation the string
> parameter to gfc_check_conformance with G_().
> * check.c (gfc_invalid_boz): Mark hint for translation using
> _(). (gfc_check_achar): Mark for translation the message
> parameter to gfc_invalid_boz using G_(). (gfc_check_char):
> Mark for translation the message parameter to gfc_invalid_boz
> using G_(). (gfc_check_complex): Mark for translation the
> message parameter to gfc_invalid_boz using G_().
> (gfc_check_float): Mark for translation the message
> parameter to gfc_invalid_boz using G_(). (check_rest): Mark
> for translation the string parameter to gfc_check_conformance
> with _(). (gfc_check_minloc_maxloc): Mark for translation
> the string parameter to gfc_check_conformance with _().
> (gfc_check_findloc): Mark for translation the string parameter
> to gfc_check_conformance with _(). (check_reduction): Mark
> for translation the string parameter to gfc_check_conformance
> with _(). (gfc_check_pack): Mark for translation the string
> parameter to gfc_check_conformance with _().
> * decl.c (match_old_style_init): Mark for translation the
> message parameter to gfc_invalid_boz using G_().
> * expr.c (gfc_check_assign): Mark for translation the string
> parameter to gfc_check_conformance with _().
> * intrinsic.c (check_specific): Mark for translation the string
> parameter to gfc_check_conformance with _().
> (gfc_check_intrinsic_standard): Mark symstd_msg strings for
> translation using G_(). No need to mark symstd_msg for
> translation in call to gfc_warning or when setting symstd.
> * io.c (check_open_constraints): Mark strings for translation
> using G_() in all calls to warn_or_error. (match_io_element):
> Mark for translation the message parameter to gfc_invalid_boz
> using G_().
> * primary.c (match_boz_constant): Mark for translation the
> message parameter to gfc_invalid_boz using G_().
> * resolve.c (resolve_elemental_actual): Mark for translation
> the string parameter to gfc_check_conformance with _().
> (resolve_operator): Mark for translation the string parameter
> to gfc_check_conformance with _(). Mark translation strings
> assigned to msg using G_() for use in a call to cfg_warning.
I believe that this is wrong
@@ -67,7 +67,7 @@ gfc_invalid_boz (const char *msg, locus *loc)
return false;
}
- const char hint[] = " [see %<-fno-allow-invalid-boz%>]";
+ const char hint[] = _(" [see %<-fno-allow-invalid-boz%>]");
fortan/lang.opt RejectNegative for allow-invalid-boz. There
is no option -fno-allow-invalid-boz.
% gfcx -fno-allow-invalid-boz -c a.f90
gfortran: error: unrecognized command-line option '-fno-allow-invalid-boz'; did
you mean '-fallow-invalid-boz'?
next prev parent reply other threads:[~2020-07-01 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 14:29 [Bug fortran/52279] New: Fortran translation issues issues burnus at gcc dot gnu.org
2013-06-29 22:24 ` [Bug fortran/52279] " dominiq at lps dot ens.fr
2020-07-01 16:08 ` [Bug fortran/52279] Fortran translation issues cvs-commit at gcc dot gnu.org
2020-07-01 21:39 ` kargl at gcc dot gnu.org [this message]
2020-07-02 10:05 ` cvs-commit at gcc dot gnu.org
2020-07-02 10:14 ` markeggleston at gcc dot gnu.org
2020-07-02 10:39 ` markeggleston at gcc dot gnu.org
2020-07-02 15:31 ` kargl at gcc dot gnu.org
2020-07-02 15:53 ` jakub at gcc dot gnu.org
2020-07-02 16:41 ` sgk at troutmask dot apl.washington.edu
2020-07-02 17:10 ` schwab@linux-m68k.org
2020-07-02 17:15 ` sgk at troutmask dot apl.washington.edu
2020-07-02 17:24 ` schwab@linux-m68k.org
2020-07-02 18:41 ` sgk at troutmask dot apl.washington.edu
2021-11-03 20:19 ` egallager 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-52279-4-qRvlTnAAIc@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).