Re: GCC 4.0.2 and PR 23993

2005-09-22 Thread Benjamin Kosnik
> > I have. I am awaiting solaris test details. > > Not very good: regressions on Solaris 2.6, 7, 8 and 9. > > FAIL: ext/mt_allocator/check_allocate_big_per_type.cc execution test > FAIL: ext/mt_allocator/check_delete.cc execution test > FAIL: ext/mt_allocator/check_new.cc execution test > FAIL:

Re: GCC 4.0.2 and PR 23993

2005-09-22 Thread Eric Botcazou
> I have. I am awaiting solaris test details. Not very good: regressions on Solaris 2.6, 7, 8 and 9. FAIL: ext/mt_allocator/check_allocate_big_per_type.cc execution test FAIL: ext/mt_allocator/check_delete.cc execution test FAIL: ext/mt_allocator/check_new.cc execution test FAIL: ext/mt_allocator

Re: GCC 4.0.2 and PR 23993

2005-09-21 Thread Mark Mitchell
Giovanni Bajo wrote: > Mark Mitchell <[EMAIL PROTECTED]> wrote: > > >>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. > >

Re: GCC 4.0.2 and PR 23993

2005-09-21 Thread Giovanni Bajo
Mark Mitchell <[EMAIL PROTECTED]> wrote: > 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 feeling is that these 4.0 rele

Re: GCC 4.0.2 and PR 23993

2005-09-21 Thread Paolo Carlini
Mark Mitchell wrote: 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. I vote for option 3., not 1. and also not 2. (sorry ;) Pao

Re: GCC 4.0.2 and PR 23993

2005-09-21 Thread Benjamin Kosnik
> 1. Release 4.0.2 without fixing this PR. (The bits are ready, sitting >on my disk.) Let's drop-kick this sucker to the ftp server already. >Has Benjamin applied his patch on the 4.0 branch? I have. I am awaiting solaris test details. -benjamin

Re: GCC 4.0.2 and PR 23993

2005-09-21 Thread 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

GCC 4.0.2 and PR 23993

2005-09-21 Thread Mark Mitchell
I'm soliciting feedback regrading a problem in the 4.0.2 release. PR 23993 is a rejects-valid C++ PR that represents a regression from GCC 4.0.1. That's particularly unfortunate; we really want to avoid introducing new breakage on the release branch. It is, sadly, more fallout from my static d