public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abe_skolnik at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug translation/66928] Typos in translatable strings
Date: Mon, 22 Apr 2024 20:16:35 +0000	[thread overview]
Message-ID: <bug-66928-4-i2iVsGO7bR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66928-4@http.gcc.gnu.org/bugzilla/>

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

Abe <abe_skolnik at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |abe_skolnik at yahoo dot com

--- Comment #2 from Abe <abe_skolnik at yahoo dot com> ---
from a recent ["Mon Apr 1 19:18:36 2024 +0100"] Git revision
["4bd2f59af4a78cdc80039cffa51c1d9ad91081a3"], and including line numbers on the
left...

———

gcc/gcov-tool.cc
————————————————
183 /* Print merge usage and exit.  */
184
185 static void ATTRIBUTE_NORETURN
186 merge_usage (void)
187 {
188   fnotice (stderr, "Merge subcommand usage:");
189   print_merge_usage_message (true);
190   exit (FATAL_EXIT_CODE);
191 }

...

505 /* Print overlap usage and exit.  */
506
507 static void ATTRIBUTE_NORETURN
508 overlap_usage (void)
509 {
510   fnotice (stderr, "Overlap subcommand usage:");
511   print_overlap_usage_message (true);
512   exit (FATAL_EXIT_CODE);
513 }



———



fortran/lang.opt
————————————————
384 faggressive-function-elimination
385 Fortran Var(flag_aggressive_function_elimination)
386 Eliminate multiple function invocations also for impure functions.

...

431 Enum
432 Name(gfc_convert) Type(enum gfc_convert) UnknownError(Unrecognized option
to endianness value: %qs)



———

... so my conclusion is "no to all 4": all 4 of the reported bugs are dead at
least of roughly April 1 2024 [no joke ;-)].

  parent reply	other threads:[~2024-04-22 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-66928-4@http.gcc.gnu.org/bugzilla/>
2021-10-28  2:55 ` egallager at gcc dot gnu.org
2024-04-22 20:16 ` abe_skolnik at yahoo dot com [this message]
2024-04-22 20:21 ` abe_skolnik at yahoo dot com
2024-04-22 20:29 ` 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-66928-4-i2iVsGO7bR@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).