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

Re: PERL_RC_STACK branch: first cut

Thread Previous | Thread Next
From:
Leon Timmermans
Date:
March 1, 2023 00:06
Subject:
Re: PERL_RC_STACK branch: first cut
Message ID:
CAHhgV8jf0VSsWANmXBuexXr04j5S=6VLzqCtbz7HoyWeSi13=g@mail.gmail.com
On Tue, Feb 28, 2023 at 11:03 AM Darren Duncan <darren@darrenduncan.net>
wrote:

> On 2023-02-27 2:50 a.m., demerphq wrote:
> > On Sun, 26 Feb 2023 at 17:06, Dave Mitchell wrote:
> >     The branch containing the first stage of my "make the stack
> ref-counted"
> >     work is nearly ready for merging. In a default build, the core is
> mostly
> >     unchanged: only when built with -DPERL_RC_STACK does it behave
> >     differently. It needs testing on Windows. I need to decide whether to
> >     merge soon or wait until after 5.38.
> >
> > I think it has to wait till 5.38, at least as far as normal policy goes.
> I guess
> > it depends on whether we consider this a contentious code-change, but
> given its
> > scale it seems like we should hold off. (It brings me no joy to say this
> BTW, id
> > be more than happy if my understanding was incorrect.)
>
> To be completely clear, in a default build, should all known XS also
> compile and
> run properly without alterations?  Or does the "mostly unchanged" exclude
> some
> things that XS may be sensitive to?
>

I would personally expect xsubpp to need updating to avoid the performance
degradation (and for PPCODE xsubs I expect they will need updating to not
have the degradation), but it should be functional without that.

Leon

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