public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] Fix translation mistakes 2023 in GCC/Rust [PR108890] Date: Tue, 2 May 2023 07:09:12 +0000 (GMT) [thread overview] Message-ID: <20230502070912.43E28385842A@sourceware.org> (raw) https://gcc.gnu.org/g:67905463cbcf8cd375c51a114367d8209d98f065 commit 67905463cbcf8cd375c51a114367d8209d98f065 Author: TieWay59 <tieway59@foxmail.com> Date: Wed Apr 19 14:07:34 2023 +0800 Fix translation mistakes 2023 in GCC/Rust [PR108890] In https://gcc.gnu.org/PR108890 "Translation mistakes 2023" @rillig lists several issues with GCC/Rust diagnostics and option help texts (but also a few non-GCC/Rust). This commit fix mistakes only related to GCC/Rust, specifically to the file `gcc/rust/lang.opt`. closes https://github.com/Rust-GCC/gccrs/issues/1916 PR translation/108890 gcc/rust/ * lang.opt: Fix translation mistakes 2023 in GCC/Rust [PR108890] (line 67): change the inconsistent tab to spaces (line 75): wrap bare placeholder `integer` (line 79): remove redundant text of `Choose which` (line 96): remove redundant text of `Choose which` (line 112): remove redundant `Flag to` (line 124): correct the exclusive term `When to stop` (line 124): correct typo of `copimlation` Signed-off-by: Tieway59 <tieway59@foxmail.com> Diff: --- gcc/rust/lang.opt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gcc/rust/lang.opt b/gcc/rust/lang.opt index aab168334f6..753cea1fbc4 100644 --- a/gcc/rust/lang.opt +++ b/gcc/rust/lang.opt @@ -64,7 +64,7 @@ Dump various Rust front end internals. frust-dump- Rust Joined RejectNegative --frust-dump-<type> Dump Rust frontend internal information. +-frust-dump-<type> Dump Rust frontend internal information. frust-incomplete-and-experimental-compiler-do-not-use Rust Var(flag_rust_experimental) @@ -72,11 +72,11 @@ Enable experimental compilation of Rust files at your own risk frust-max-recursion-depth= Rust RejectNegative Type(int) Var(rust_max_recursion_depth) Init(64) --frust-max-recursion-depth=integer +-frust-max-recursion-depth=<integer> frust-mangling= Rust Joined RejectNegative Enum(frust_mangling) Var(flag_rust_mangling) --frust-mangling=[legacy|v0] Choose which version to use for name mangling +-frust-mangling=[legacy|v0] Version to use for name mangling Enum Name(frust_mangling) Type(int) UnknownError(unknown rust mangling option %qs) @@ -93,7 +93,7 @@ Rust Joined RejectNegative frust-edition= Rust Joined RejectNegative Enum(frust_edition) Var(flag_rust_edition) --frust-edition=[2015|2018|2021] Choose which edition to use when compiling rust code +-frust-edition=[2015|2018|2021] Edition to use when compiling rust code Enum Name(frust_edition) Type(int) UnknownError(unknown rust edition %qs) @@ -109,7 +109,7 @@ Enum(frust_edition) String(2021) Value(2) frust-embed-metadata Rust Var(flag_rust_embed_metadata) -Flag to enable embeding metadata directly into object files +Enable embedding metadata directly into object files frust-metadata-output= Rust Joined RejectNegative @@ -121,7 +121,7 @@ Rust Joined Separate frust-compile-until= Rust Joined RejectNegative Enum(frust_compile_until) Var(flag_rust_compile_until) --frust-compile-until=[ast|attributecheck|expansion|nameresolution|lowering|typecheck|privacy|unsafety|const|copimlation|end] When to stop in the pipeline when compiling Rust code +-frust-compile-until=[ast|attributecheck|expansion|nameresolution|lowering|typecheck|privacy|unsafety|const|compilation|end] The pipeline will run up until this stage when compiling Rust code Enum Name(frust_compile_until) Type(int) UnknownError(unknown rust compile-until %qs)
reply other threads:[~2023-05-02 7:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230502070912.43E28385842A@sourceware.org \ --to=tschwinge@gcc.gnu.org \ --cc=gcc-cvs@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).