[nvptx, PR81352] Add exit insn after noreturn call for neutered threads in warp

[Gerald Pfeifer]

On Wed, 24 Jan 2018, Tom de Vries wrote:
> On 01/24/2018 12:53 PM, Richard Biener wrote:
>> wrong-code bugs qualify for stage4 if a fix isn't too invasive.  Target
>> maintainers have an extra say to override stage4 rules anyway and for
>> non-primary/secondary targets nobody cares anyway.
> Maybe then we should be more clear then in formulation of stage 4 criteria?

Richi?  I did not see anyone approve or reject Tom's patch, and it
did not make it into the tree.

What is your take?  (It's fine as far as wwwdocs go, but this really
is a question on the RMs.)

Gerald

> [ Change validated as XHTML 1.0 Transitional ]
> 
> Index: htdocs/develop.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/develop.html,v
> retrieving revision 1.178
> diff -u -r1.178 develop.html
> --- htdocs/develop.html	15 Jan 2018 08:23:26 -0000	1.178
> +++ htdocs/develop.html	24 Jan 2018 13:40:30 -0000
> @@ -130,10 +130,10 @@
>  <h4><a name="stage4">Stage 4</a></h4>
> 
>  <p>During this period, the only (non-documentation) changes that may
> -be made are changes that fix regressions.  Other changes may not be
> -done during this period.  Note that the same constraints apply
> -to release branches.  This period lasts until stage 1 opens for
> -the next release.</p>
> +be made are changes that fix regressions, or that fix wrong-code bugs
> +in a non-invasive way.  Other changes may not be done during this
> +period.  Note that the same constraints apply to release branches.
> +This period lasts until stage 1 opens for the next release.</p>
> 
>  <p><strong>Rationale</strong></p>