[PATCH] gcc-wwwdocs: Mention check-c++-all target for C++ front end patch testing

[Jason Merrill]

On 10/2/24 4:51 AM, Simon Martin wrote:
> This is a follow-up to the discussion about testing changes to the C++
> front end in
> https://gcc.gnu.org/pipermail/gcc-patches/2024-October/664258.html
> 
> It also clarifies that the make invocation examples should be made from
> the *build* tree.
> 
> Validated fine via https://validator.w3.org.

OK.

> ---
>   htdocs/contribute.html | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/htdocs/contribute.html b/htdocs/contribute.html
> index 53c27c6e..3ab65323 100644
> --- a/htdocs/contribute.html
> +++ b/htdocs/contribute.html
> @@ -111,9 +111,17 @@ For a normal native configuration, running</p>
>   make bootstrap
>   make -k check
>   </pre></blockquote>
> -<p>from the top level of the GCC tree (<strong>not</strong> the
> +<p>from the top level of the GCC build tree (<strong>not</strong> the
>   <code>gcc</code> subdirectory) will accomplish this.</p>
>   
> +<p>If your change is to the C++ front end, you need to run the C++ testsuite
> +in all standard conformance levels. For a normal native configuration,
> +running</p>
> +<blockquote><pre>
> +make -C gcc -k check-c++-all
> +</pre></blockquote>
> +<p>from the top level of the GCC build tree will accomplish this.</p>
> +
>   <p>If your change is to a front end other than the C or C++ front end,
>   or a runtime library other than <code>libgcc</code>, you need to verify
>   only that the runtime library for that language still builds and the