develooper Front page | perl.perl5.porters | Postings from March 2013

Re: smoking PERL_OLD_COPY_ON_WRITE 3.5.0-22-generic [debian](x86_64/8 cpu) {blead_g++}

Thread Previous | Thread Next
From:
Dave Mitchell
Date:
March 23, 2013 21:38
Subject:
Re: smoking PERL_OLD_COPY_ON_WRITE 3.5.0-22-generic [debian](x86_64/8 cpu) {blead_g++}
Message ID:
20130323213753.GH2409@iabyn.com
On Sat, Mar 23, 2013 at 03:33:24PM -0400, George Greer wrote:
> On Mon, 18 Mar 2013, Dave Mitchell wrote:
> 
> >On Sun, Mar 17, 2013 at 04:38:00PM -0400, George Greer wrote:
> >>O O O X X X -Duseithreads -Accflags=-DPERL_OLD_COPY_ON_WRITE
> >
> >I wonder if there's any point in smoking PERL_OLD_COPY_ON_WRITE
> >any more? I presume it been superseded for all practical purposes by
> >PERL_NEW_COPY_ON_WRITE?
> >
> >Instead, while PERL_NEW_COPY_ON_WRITE is temporarily not the default
> >(till after 5.18), perhaps we should smoke that as an option instead?
> >
> >(The OLD has a couple of consistent failures, which I suspect no one will
> >be in a hurry to fix).
> 
> I switch over to _NEW_ and still some failures:
> 
> clang:
> http://www.mail-archive.com/daily-build-reports@perl.org/msg135696.html
> 
> g++:
> http://www.mail-archive.com/daily-build-reports@perl.org/msg135685.html

Thanks for the links.
I've just pushed some commits which hopefully fix the Peek.t failure,
and add more instrumentation to require.t so it may be clearer why its
failing.

-- 
That he said that that that that is is is debatable, is debatable.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About