Closed
Description
Carlos Guevara has sent me a list of CPAN distributions which are failing tests against Perl 5 blead. I am trying to bisect these failures now. Since I suspect that more than one distribution will be broken by certain particular commits, I'm opening a separate ticket for each bad commit.
Log::Trace
Bisecting with this invocation:
$ perl Porting/bisect.pl \
--start=v5.41.8 \
--end=8d462f6a9e96adf5dac36c7e778468b78a47be96 \
--module=Log::Trace
... I got:
b9eeeef8c043fb0238a07e64636815bf327a6562 is the first bad commit
commit b9eeeef8c043fb0238a07e64636815bf327a6562
Author: Lukas Mai <l.mai@web.de>
Date: Fri Feb 14 21:49:03 2025 +0100
Commit: Lukas Mai <l.mai@web.de>
CommitDate: Sun Feb 16 01:42:36 2025 +0100
op.c: re-enable coderef-in-stash optimization
When seeing 'sub foo { ... }', perl does not need to allocate a full
typeglob (with the subroutine being stored in the CODE slot). Instead,
it can just store a coderef directly in the stash.
@mauke, please take a look.
For reference: The breaking commit was:
$ git describe
v5.41.8-98-gb9eeeef8c0
As I write this blead is at:
$ git describe
v5.41.8-119-g8d462f6a9e
Note: Right now the CPANtesters database is having difficulty receiving reports. So responding to BBC tickets is going to be more tedious than usual. See: https://www.nntp.perl.org/group/perl.cpan.testers.discuss/2025/02/msg4654.html.