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 c/114364] Untranslatable string 'in intervening code' Date: Tue, 19 Mar 2024 08:13:20 +0000 [thread overview] Message-ID: <bug-114364-4-vXZNZ233KX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114364-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114364 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:8959ab63f1881a8a4b1921b946d4ea3986bf1063 commit r14-9534-g8959ab63f1881a8a4b1921b946d4ea3986bf1063 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Mar 19 09:10:26 2024 +0100 openmp: Make c_omp_check_loop_binding_exprs diagnostics translatable [PR114364] c_omp_check_loop_binding_exprs with check_loop_binding_expr was composing diagnostics from a format string with %s that provided additional words (but not keywords). That is a big no no for translations, both because the translator can't choose a different word order and because the %s part wasn't translated at all (would need to use _("...") to get translated), so this patch rewrites it such that the whole messages are in the format strings. 2024-03-19 Jakub Jelinek <jakub@redhat.com> PR c/114364 * c-omp.cc (enum check_loop_binding_expr_ctx): New type. (check_loop_binding_expr): Remove context argument, add ctx argument with check_loop_binding_expr_ctx type at the end. Don't create diagnostic message from multiple pieces. (c_omp_check_loop_binding_exprs): Adjust callers.
next prev parent reply other threads:[~2024-03-19 8:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 15:28 [Bug c/114364] New: " roland.illig at gmx dot de 2024-03-16 15:32 ` [Bug c/114364] " roland.illig at gmx dot de 2024-03-16 16:00 ` jakub at gcc dot gnu.org 2024-03-17 21:45 ` roland.illig at gmx dot de 2024-03-19 8:13 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-19 8:20 ` jakub 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-114364-4-vXZNZ233KX@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).