public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-7767] [nvptx] Add mexperimental Date: Tue, 22 Mar 2022 13:40:50 +0000 (GMT) [thread overview] Message-ID: <20220322134050.4BEE83947411@sourceware.org> (raw) https://gcc.gnu.org/g:a4baa0d3c5ad66e5ec24b8b5db7042739f0290aa commit r12-7767-ga4baa0d3c5ad66e5ec24b8b5db7042739f0290aa Author: Tom de Vries <tdevries@suse.de> Date: Sat Mar 19 17:40:55 2022 +0100 [nvptx] Add mexperimental Add new option -mexperimental. This allows, rather than developing a new feature to completion in a development branch, to develop a new feature on trunk, without disturbing trunk. The equivalent of the feature branch merge then becomes making the functionality available for -mno-experimental. If more features at the same time will be developed, we can do something like -mexperimental=feature1,feature2 but for now that's not necessary. For now, has no effect. gcc/ChangeLog: 2022-03-19 Tom de Vries <tdevries@suse.de> * config/nvptx/nvptx.opt (mexperimental): New option. Diff: --- gcc/config/nvptx/nvptx.opt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/config/nvptx/nvptx.opt b/gcc/config/nvptx/nvptx.opt index 980428b58cc..11288d1a8ee 100644 --- a/gcc/config/nvptx/nvptx.opt +++ b/gcc/config/nvptx/nvptx.opt @@ -88,3 +88,6 @@ Target Var(nvptx_comment) Init(1) Undocumented malias Target Var(nvptx_alias) Init(0) Undocumented + +mexperimental +Target Var(nvptx_experimental) Init(0) Undocumented
reply other threads:[~2022-03-22 13:40 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=20220322134050.4BEE83947411@sourceware.org \ --to=vries@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).