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] Move '-frust-incomplete-and-experimental-compiler-do-not-use' out of the middle of '-frust-mangling=
Date: Thu,  8 Dec 2022 08:00:13 +0000 (GMT)	[thread overview]
Message-ID: <20221208080013.57AE93883F06@sourceware.org> (raw)

https://gcc.gnu.org/g:d9d9ca0b9e50b669d5445e028739bcdd0aa024bd

commit d9d9ca0b9e50b669d5445e028739bcdd0aa024bd
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Wed Dec 7 09:14:33 2022 +0100

    Move '-frust-incomplete-and-experimental-compiler-do-not-use' out of the middle of '-frust-mangling=[...]'

Diff:
---
 gcc/rust/lang.opt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/rust/lang.opt b/gcc/rust/lang.opt
index 155892d0027..ff4f5375daa 100644
--- a/gcc/rust/lang.opt
+++ b/gcc/rust/lang.opt
@@ -66,6 +66,10 @@ frust-dump-
 Rust Joined RejectNegative
 -frust-dump-<type>	Dump Rust frontend internal information.
 
+frust-incomplete-and-experimental-compiler-do-not-use
+Rust Var(flag_rust_experimental)
+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
@@ -74,10 +78,6 @@ 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-incomplete-and-experimental-compiler-do-not-use
-Rust Var(flag_rust_experimental)
-Enable experimental compilation of Rust files at your own risk
-
 Enum
 Name(frust_mangling) Type(int) UnknownError(unknown rust mangling option %qs)

                 reply	other threads:[~2022-12-08  8:00 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=20221208080013.57AE93883F06@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: 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).