bulk88
bulk88
Research notes: For the first time ever, I saw MSVC 2022 -O1 inline a `newSV_type_mortal(SVt_PV);` statement on its own free will, IDK how this happened. `newAV();` for some reason, is...
troll argument: will this "break" or change flaky PP single stepping to extra crispy flaky PP single stepping? I don't have the time to compile this PR and do a...
Also, more seriously, would this optimization degrade or break [NYTProf?](https://metacpan.org/pod/Devel::NYTProf) ?
> > What I don't understand is why that compiler hasn't complained about all the other I32 stack stuff we do. For example we have a plenty of code like...
> On Thu, 23 Jan 2025 02:13:38 -0800, bulk88 ***@***.***> wrote: > Module: NOT!!!! Config.pm > > **Description** > > [#21135](https://github.com/Perl/perl5/issues/21135) "Errno archname/osvers too strict. " > > I know...
> Burn Config::Perl::V.pm's features into libperl.so, delete > Config::Perl::V.pm from p5p git repo. > Config::Perl::V existed way before integrated into core to be able to > uniquely identify smoke reports...
> Ideologically it does sound bad/unclean, but I don't think any Bank software is going to be gating "send all my money" on perl version. Any Makefile.PL checks will crash...
> That is an awful lot of info that I find hard to grasp, but I am triggered by > Config::Perl::V in combination with unsafe > > Is Config::Perl::V unsafe?...
> (Also, I wonder whether there are any legitimate post-build modifications of _Config.pm_ that happen out there? Such as part of an automated deployment, packaging, or some customisation process.) This...
> I'm sure this could vary depending upon user environment & threat model, but my thoughts are: > > * Unless there's a compelling reason otherwise, if "_user with write...