This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: "Experimental" features in releases
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 17 Apr 2006 15:31:29 -0400
- Subject: Re: "Experimental" features in releases
- References: <4443E3EA.7000508@codesourcery.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark Mitchell wrote:
> Thoughts?
>
I don't know which of the loop linear transformations you folks were
debating (the loop linear stuff defines a family of transformations),
but I vote for having no experimental features in releases.
If a feature is meant to be activated with -Ox or with -f/-m switches,
it should only be present in a release if we are prepared to support it.
In this case, based on Dan's analysis I vote for moving the non-working
code into a branch and allow it to mature. Particularly, if it has not
been around for long.
Alternately, we could have a sanitization process during releases that
enables a warning message inside the gate_*() functions for experimental
passes. But, not every feature can be enabled/disabled with a gating
function and it becomes a slippery slope.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEQ+0RUTa2oAUaiwQRAlpFAJ0cUkDBW0Bf0COa6tMS9RJOReopLACgjWPV
0q7N9OeVgDpUVE47mhQ/W4A=
=Fxlp
-----END PGP SIGNATURE-----