| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
perl (in theory) supports C89, where expl() doesn't exist (though
long doubles do), so our tests shouldn't fail if expl() isn't
available.
Of course, the NetBSD libm does supply an implementation of expl(),
it's just not a long double implementation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On m68k, the natural alignment is 16 bits which causes the opslab_opslot
member of struct opslab to be aligned at a 16-bit offset. Other 32-bit
and 64-bit architectures have a natural alignment of at least 32 bits, so
the offset is always guaranteed to be at least 32-bit-aligned.
Fix this by adding additional padding bytes before the opslab_opslot
member, both for cases when PERL_DEBUG_READONLY_OPS defined and not
defined to ensure the offset of oplab_slots is always 32-bit-aligned.
On architectures which have a natural alignment of at least 32 bits,
the padding does not affect the alignment, offsets or struct size.
|
|
|
|
|
|
| |
* YAPC was rebranded.
* OSCON and OSDC are discontinued.
* The Perl Review calendar link doesn't work.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Commit f46dcac2d383af532d3e8c014488fba83a514309 changed the I32
arguments of Perl_utf16_to_utf8() to Size_t and updated all callers
that called it via the utf16_to_utf8 macro, but missed the
fully-qualified call in cygwin.c.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* CVE-2020-10543
* CVE-2020-10878
* CVE-2020-12723
They were fixed on v5.28.3 and 5.30.3 and the fixes were backported.
|
|
|
|
| |
How this should behave is not well defined.
|
|
|
|
|
| |
This had ASCII-centric tests, which have now been converted to work on
EBCDIC as well.
|
| |
|
|
|
| |
As suggested in #16910
|
|
|
| |
The 2 no-longer-needed warning categories were mentioned with each other's changes.
|
|
|
| |
Addresses #16910 plus other minor updates.
|
| |
|
| |
|
|
|
|
| |
also add a debug statement for viewing GitHub context
|
|
|
|
|
|
|
|
| |
Smoke informations should belong to the testsuite
and only display when run on the main repo.
Note: moved the 'if' condition in the run as a 'if:'
check, avoiding to start a VM when not needed.
|
|
|
|
|
|
| |
This is avoiding using too much resources on fork repositories.
fixup
|
|
|
|
|
|
|
|
|
|
|
| |
Abort earlier if we cannot compile a simple
configuration on linux.
This is avoiding wasting resources and will come
back earlier on errors. Note that this is adding
the time of an extra runtime job as we are
waiting for the sanity_check workflow before starting
any other jobs.
|
|
|
|
|
|
| |
The existing smoke-* workflows are part of the testsuite.
By merging them together we can link them and add some
conditions to reduce resources usages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This resolves #17774.
This ticket is because the fixes in GH #17154 failed to get every case,
leaving this one outlier to be fixed by this commit.
The text in https://github.com/Perl/perl5/issues/17154 gives extensive
details as to the problem. But briefly, in an attempt to speed up
interpreter cloning, I moved certain SVs from interpreter level to
global level in e80a0113c4a8036dfb22aec44d0a9feb65d36fed (v5.27.11,
March 2018). This was doable, we thought, because the content of these
SVs is constant throughout the life of the program, so no need to copy
them when cloning a new interpreter or thread. However when an
interpreter exits, all its SVs get cleaned up, which caused these to
become garbage in applications where another interpreter remains
running. This circumstance is rare enough that the bug wasn't reported
until September 2019, #17154. I made an initial attempt to fix the
problem, and closed that ticket, but I overlooked one of the variables,
which was reported in #17774, which this commit addresses.
Effectively the behavior is reverted to the way it was before
e80a0113c4a8036dfb22aec44d0a9feb65d36fed.
|
| |
|
|
|
|
| |
(cherry picked from commit aaae777fa09e60c0fe9cb0c3e9f004c7c2a8f6ee)
|
|
|
|
| |
(cherry picked from commit 05ddfb3ce88adc105dcaf875d4e0ae32f2f05048)
|
|
|
|
| |
(cherry picked from commit ae49126f3ca2352fb49d7121a769189bf31e6f72)
|
|
|
|
| |
(cherry picked from commit 2d489145cbf021228a2a819dab4208e16d1049c6)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As described in #17743, study_chunk can re-enter itself either by
simple recursion or by enframing. 089ad25d3f used the new mutate_ok
variable to track whether we were within the framing scope of GOSUB,
and to disallow mutating changes to ops if so.
This commit extends that logic to reentry by recursion, passing in
the current state as was_mutate_ok.
(CVE-2020-12723)
(cherry picked from commit 3445383845ed220eaa12cd406db2067eb7b8a741)
|