(math/p5-PDL) Updated 2.024 to 2.100
2.100 2025-03-27
- fix Math function prototypes for GCC 15 (#528) - thanks @jplesnik for report
- Basic::rvals to allow Centre as ndarray (#532) - thanks @wlmb
- now an error to qsort{,vec} complex data
- {and,or}over output type now same as input type (#533)
- add Ufunc::{b,}xorover (#533) - thanks @jo-37
- fix Math::polyroots crashing on [2 1 0 1] (#536) - thanks @pipatron for report
- fix Slices::indexND with an empty used as an lvalue (#535) - thanks @yelnats for report
- many fixes and improvements to the auto-generated POD docs (#534) - thanks @jo-37
2.099 2025-01-23
- fix test that assumed acosh(0)->byte, i.e. nan()->byte, was always 0 (#514) - thanks @eserte for report
- separate PDL::Type POD documentation
- partly restoring pre-2.096 xform type-selection: if xform given no typed outputs, and non-available (greater than last-given type) typed inputs, use last-given (#511, https://github.com/moocow-the-bovine/PDL-CCS/issues/18)
- fix Math::polyroots with native-complex input and supplied null output
- add Pars type-spec "!real" which makes it an error to supply real values (#511)
- now an error to call Ops::carg on a real value, or Ops::czip on complex inputs (#511)
[813 lines not shown]
Add a detach call to the CFATTACH_ define mostly so that the children
so the right thing. This isn't very useful right now, but will become
more useful with a driver that will be landing in the near future.
nouveau(4): Fix return value of fence wait.
kpause(9) returns EAGAIN/EWOULDBLOCK when it times out, which is
perfectly normal and expected here with an internal one-tick timeout
which should just go through another loop iteration. This function
is expected to return the number of ticks left to wait when done, so
it reports timeout by returning zero, and is forbidden to fail with
EAGAIN/EWOULDBLOCK.
This is also forbidden to fail with EINTR -- on interruption it must
fail with the Linux ERESTARTSYS instead. So map EINTR to that too
while here.
PR kern/59773: i386 11.0_BETA system crash (Xorg nouveau ?)
aes(9): New aes_keysched_enc/dec.
These implement the standard key schedule. They are named
independently of any particular AES implementation, so that:
(a) we can swap between the BearSSL aes_ct and aes_ct64 code without
changing all the callers who don't care which one they get, and
(b) we could push it into the aes_impl abstraction if we wanted.
This eliminates all br_aes_* references outside aes_bear.c, aes_ct*.c,
and the new aes_keysched.c wrappers.
Preparation for:
PR kern/59774: bearssl 32-bit AES is too slow, want 64-bit optimized
version in kernel
hunspell: Fix a ctype(3) abuse
There are probably other ctype(3) abuses but "-Wall" does not seem to
work when <cctype> is included because the macros get undef-ed and
that one was exercised the hard way via `hunspell -t`.
PKGREVISION++
tests/lib/libpthread: Don't abuse xfail.
Use a signal handler to check for SIGABRT, rather than
atf_tc_expect_signal.
xfail is for when there is a bug that we haven't fixed yet and the
test manifests a symptom of that bug -- a list of xfails is a list of
open bugs to be fixed. In this case, we are verifying that
pthread_create _correctly_ raises SIGABRT (or fails with nonzero
return code -- both are acceptable outcomes, really), and there is no
bug here at the moment.
Prompted by (but unrelated to):
PR lib/59784: dlopening and dlclosing libpthread is broken
tests/lib/libpthread: Test unloading libpthread after lazy binding.
If you dlopen libpthread and dlclose it again, the thread stubs like
pthread_mutex_lock need to continue working -- a library might have
calls to it in order to support thread-safety for threaded
applications, but that library needs to continue working even in
non-threaded applications after lazy binding of the libpthread symbol
instead of the libc stub.
PR lib/59784: dlopening and dlclosing libpthread is broken
py-exceptiongroup: updated to 1.3.1
1.3.1
- Fixed ``AttributeError: 'TracebackException' object has no attribute 'exceptions'``
when formatting unpickled TBEs from another Python process which did not apply the
``exceptiongroup`` patches
pmap_pte_alloc() expects to be called while in a critical section, but
pmap_enter() was entering the critical section after calling pmap_pte_alloc().
Fix that.
There's no practical impact of this change at this time, but code code and
the comments should at least be consistent.
