Hi, 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. Committed to trunk. Thanks, - Tom [nvptx] Add mexperimental gcc/ChangeLog: 2022-03-19 Tom de Vries <tdevr...@suse.de> * config/nvptx/nvptx.opt (mexperimental): New option. --- 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