[Perl/perl5]
Branch: refs/heads/yves/update_to_Encode_3_17 Home: https://github.com/Perl/perl5
[Perl/perl5] 1486ec: hv.* - disable unshared keys except when requested
Branch: refs/heads/yves/disable_by_default_unshared_hashes Home: https://github.com/Perl/perl5 Commit: 1486ecb907ca14fd8111a904e65bd514e044f882 https://github.com/Perl/perl5/commit/1486ecb907ca14fd8111a904e65bd514e044f882 Author: Yves Orton Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M hv.c M hv.h Log Message: --- hv.* - disable unshared keys except when requested This disables the new unshared hash key logic by default. People who wish to try it out can enable it at build time with -DPERL_USE_UNSHARED_KEYS_IN_LARGE_HASHES in the configure process.
[Perl/perl5]
Branch: refs/heads/yves/disable_by_default_unshared_hashes Home: https://github.com/Perl/perl5
[Perl/perl5] bb5e77: Accept \p{nv=-0}
Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: bb5e773d6fb68865d8e2c5a392215c27c7b49636
https://github.com/Perl/perl5/commit/bb5e773d6fb68865d8e2c5a392215c27c7b49636
Author: Karl Williamson
Date: 2022-04-08 (Fri, 08 Apr 2022)
Changed paths:
M regcomp.c
M t/lib/croak/regcomp
M t/re/re_tests
Log Message:
---
Accept \p{nv=-0}
Some platforms already ignore the minus sign. The Unicode standard says
the minus sign should be ignored always.
(But always doing so would cause it to not properly get the only
negative numeric value character in Unicode; I have submitted a ticket
to Unicode about this. Nevertheless, it is in keeping with the letter
and spirit of the standard for the leading minus to be ignored for -0)
[Perl/perl5] 3be5b3: threads/t/stack*.t: Add is() fcn
Branch: refs/heads/blead Home: https://github.com/Perl/perl5 Commit: 3be5b33e30b54e62002abd6d1e772e3ee110e89e https://github.com/Perl/perl5/commit/3be5b33e30b54e62002abd6d1e772e3ee110e89e Author: Karl Williamson Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M dist/threads/t/stack.t M dist/threads/t/stack_env.t Log Message: --- threads/t/stack*.t: Add is() fcn These tests roll their own ok() functions, which is ok until there is a failure, and you don't know what the failing value is. So add an is() wrapper to them that does return the expected and actual values. Commit: 601bde632530766686cd3bd4ce0b3a823b87e53d https://github.com/Perl/perl5/commit/601bde632530766686cd3bd4ce0b3a823b87e53d Author: Karl Williamson Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M dist/threads/t/stack.t M dist/threads/t/stack_env.t Log Message: --- /threads/t/stack*.t: Use mnemonics Use mnemonics instead of hard-coded numbers throughout. Commit: 31898f8b00349cec9507fc23a1899d8e2e457ca7 https://github.com/Perl/perl5/commit/31898f8b00349cec9507fc23a1899d8e2e457ca7 Author: Karl Williamson Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M dist/threads/t/stack.t M dist/threads/t/stack_env.t Log Message: --- threads/t/stack* Generalize larger min stack sizes This changes the tests so that they will work on systems that require larger minimum stack sizes than what we initially try. The initial test is skipped in this case, but the rest of the tests are adjusted from the new information. This was the least disruptive way I could come up with that didn't assume things worked correctly before running the tests, yet still adapted to a platform that has a larger minimum requirement than we guess. One could increase the initial guess to the maximum of any box found so far (this would mean doubling it in this case), but what happens if a larger case comes around? Commit: 0eeeceed10b2ab27746282e8cfb05afb1549d925 https://github.com/Perl/perl5/commit/0eeeceed10b2ab27746282e8cfb05afb1549d925 Author: Karl Williamson Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M dist/threads/t/stack.t M dist/threads/t/stack_env.t Log Message: --- threads/t/stack*: Add comment I noticed that the first real test in each of these could succeed by happenstance even if the implementation is broken. If the numbers we use happen to be the same as the system default, we'll get true even if the system ignored the request to use our numbers. Fixing the test is a chicken and egg problem, as to find out what the default value is requires using the functions the test files are trying to test. A unit could be added to Configure, but that seems too much work for just this purpose. The comments added by this commit suggest using an out-of-the-ordinary value instead of the power of 2 one that is currently used. That would minimize the likelihood of happenstance. Compare: https://github.com/Perl/perl5/compare/df12890b5e8c...0eeeceed10b2
[Perl/perl5] 13138a: jkeenan votes for 1 backport in each of 5.32 and 5.34
Branch: refs/heads/maint-votes Home: https://github.com/Perl/perl5 Commit: 13138a5efd2977f354e8fef77ef13dffa1039448 https://github.com/Perl/perl5/commit/13138a5efd2977f354e8fef77ef13dffa1039448 Author: James E Keenan Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M votes-5.32.xml M votes-5.34.xml Log Message: --- jkeenan votes for 1 backport in each of 5.32 and 5.34
[Perl/perl5] fce47e: Propose Compress-Raw-Zlib CVE fix for backporting
Branch: refs/heads/maint-votes Home: https://github.com/Perl/perl5 Commit: fce47e268477d5d05b180eff0227cb622b09be97 https://github.com/Perl/perl5/commit/fce47e268477d5d05b180eff0227cb622b09be97 Author: Steve Hay Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M votes-5.32.xml M votes-5.34.xml Log Message: --- Propose Compress-Raw-Zlib CVE fix for backporting Suggested by Jim and others on PR#19590 Commit: 0bd51548d9268647912d95f59d015a3fff033dbe https://github.com/Perl/perl5/commit/0bd51548d9268647912d95f59d015a3fff033dbe Author: Steve Hay Date: 2022-04-08 (Fri, 08 Apr 2022) Changed paths: M votes-5.34.xml Log Message: --- Remove old milestone Compare: https://github.com/Perl/perl5/compare/f6713b81c18b...0bd51548d926
