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] session-manager: Add fatal_error when flag is not present Date: Thu, 8 Dec 2022 07:59:37 +0000 (GMT) [thread overview] Message-ID: <20221208075937.BB55C3945E04@sourceware.org> (raw) https://gcc.gnu.org/g:ddd1b481a0b655716b06962053712fad7f8efa7b commit ddd1b481a0b655716b06962053712fad7f8efa7b Author: Arthur Cohen <arthur.cohen@embecosm.com> Date: Mon Nov 28 18:22:34 2022 +0100 session-manager: Add fatal_error when flag is not present Diff: --- gcc/rust/rust-session-manager.cc | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/gcc/rust/rust-session-manager.cc b/gcc/rust/rust-session-manager.cc index 79bf5527965..d9e4ce06fe7 100644 --- a/gcc/rust/rust-session-manager.cc +++ b/gcc/rust/rust-session-manager.cc @@ -429,7 +429,23 @@ Session::compile_crate (const char *filename) { #ifdef RUST_RELEASE if (!flag_rust_experimental) - gcc_unreachable (); + rust_fatal_error ( + Location (), "%s", + "gccrs is not yet able to compile Rust code " + "properly. Most of the errors produced will be gccrs' fault and not the " + "crate you are trying to compile. Because of this, please reports issues " + "to us directly instead of opening issues on said crate's " + "repository.\n\nOur github repository: " + "https://github.com/rust-gcc/gccrs\nOur bugzilla tracker: " + "https://gcc.gnu.org/bugzilla/" + "buglist.cgi?bug_status=__open__&component=rust&product=gcc\n\n" + "If you understand this, and understand that the binaries produced might " + "not behave accordingly, you may attempt to use gccrs in an experimental " + "manner by passing the following flag:\n\n" + "`-frust-incomplete-and-experimental-compiler-do-not-use`\n\nFor " + "cargo-gccrs, this means passing\n\n" + "GCCRS_EXTRA_FLAGS=\"-frust-incomplete-and-experimental-compiler-do-not-" + "use\"\n\nas an environment variable."); #endif RAIIFile file_wrap (filename);
reply other threads:[~2022-12-08 7:59 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=20221208075937.BB55C3945E04@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).