GCC 4.0.2 and PR 23993

[Eric Botcazou]

> So, my options are:
>
> 1. Release 4.0.2 without fixing this PR.  (The bits are ready, sitting
>    on my disk.)
>
> 2. Apply the patch, respin the release, and release it.
>
> 3. Apply the patch, spin RC3, and go through another testing cycle.
>
> My current plan is (2) because I think that this is an important bug
> and because I think the patch is safe and, in particular, highly
> unlikely to introduce any follow-on problems of its own.  However, I
> realize that I can't be entirely objective about this situation, so
> I'd appreciate any feedback.

Has Benjamin applied his patch on the 4.0 branch?  If so, my feeling is that 
RC3 would not be superfluous.

-- 
Eric Botcazou