[PATCH] issues with configure --enable-checking option

[Jakub Jelinek]

On Tue, Feb 25, 2020 at 11:20:58AM +0300, Roman Zhuykov wrote:
> Sandra and Richard, thank you for review!
> 
> Since 'types' checks are included into 'yes' and I addressed all other
> hints, I have pushed updated patch as r10-6832.
> 
> Jakub, Richard B, can I apply it to 8 and 9 ?

Yes.

> +When the option is not specified, the active set of checks depends on
> context.
> +Namely, bootstrap stage 1 defaults to @samp{--enable-checking=yes}, builds
> +from release archives default to @samp{--enable-checking=release}, and

Is archives the right word?  The --enable-checking=release by default is
turned on whenever it is a release branch, checked by whether gcc/DEV-PHASE
is not experimental, and generally applies to everything but the GCC trunk.

> +The @samp{valgrind} check requires the external @command{valgrind}
> simulator,
> +available from @uref{http://valgrind.org/}.  The @samp{df}, @samp{rtl},
> +@samp{gcac} and @samp{valgrind} checks are very expensive.

I would certainly not say that rtl checking is very expensive, it is
somewhat expensive, but I'm using it in all my bootstraps and others are as
well.  On the other side, fold checking is extremely expensive.

So perhaps

The @samp{rtl} checks are expensive and the @samp{df},
@samp{fold}, @samp{gcac} and @samp{valgrind} checks are very expensive.

?

	Jakub