Import tzdata2026c from locally built tzdata2026cgtz.tar.gz
The real tzdata2026cgtz.tar.gz is not yet available (Europe in July!)
so I made a version which I think should be it. If there happen to
be any material differences when the real one appears, I will do an
update. Any irrelevant differences can just wait until next time.
Summary of changes in tzdata2026c (2026-07-08 10:23:58 -0700):
* Alberta’s 2026-03-08 spring forward was its last foreseeable clock
change, as it moved to permanent -06 thereafter.
* Although another TZDB release will likely be needed soon because
Northwest Territories will likely follow Alberta, the legal
formalities have not yet taken place.
* Morocco plans to move back to permanent UTC, without daylight
saving time transitions, on 2026-09-20 at 02:00.
* Changes to commentary.
tzdata2netbsd - minor updates
Add a few \n's missing from printf's that rarely (if ever) get used.
Add a new message before comparing files, so if there are differences
it is clear which file the differences are in. When doing that, ignore
any patch remnant files that might have been left around by accident.
lang/gcc12: pull over the changes to rs6000/netbsd.h from our in-tree gcc.
This is so that this builds and runs on powerpc/11.0*.
The most important fix is that on powerpc, -msecure-plt is enabled by
default, so that resulting executables can be run with PAX_MPROTECT active.
Otherwise, we end up with executables with sections which have both
"write" and "execute" turned on, which PAX_MPROTECT rejects.
Fixes PR#60439.
Bump PKGREVISION for both gcc12 and gcc12-libs, to adhere to rules in comments.
base64_encode(): avoid reading off end of clear
Don't read clear[i+2] without bounds checking,
which can occur when (len % 3) == 1.
Issue reported in private email by "Acts1631",
and confirmed with gcc15 asan and a test harness.
p5-Data-Alias: update to 1.30.
1.30 2026-03-11 XMATH
- Use isGV_with_GP_on when available. (RT 173582)
1.29 2026-02-02 XMATH
- Fix compatibility with perl 5.43.8 (contributed by mauke)
ld.elf_so: Fix ASSERT macro in xmalloc.c.
1. Use #p, not "p", in the expansion of #define ASSERT(p), for C as of
this millennium.
2. Consistently make ASSERT(...) a single expression.
Prompted by enabling MALLOC_DEBUG to track down issues in:
PR lib/59751: dlclose is not MT-safe depending on the libraries
unloaded
ld.elf_so: Fix more races with recursive threaded dlopen/dlclose.
1. When loading an object, keep track of a finer-grained state for
relocation so that a concurrent _rtld_relocate_objects doesn't
relocate an object too early (e.g., while waiting in
_rtld_load_needed_objects for an object that is concurrently being
dlclosed to finish before we can map it afresh) leading to
spurious symbol resolution failures:
- OBJRELOC_NONE (0): object has been created but the rtld state
isn't enough to attempt relocation yet (either not all DT_NEEDED
entries have been resolved, or the dldags lists have not yet
been populated)
- OBJRELOC_READY (1): object has been created and rtld state is
ready to relocate (all DT_NEEDED entries have been resolved and
the dldags lists have been populated), but object has not yet
been relocated.
[44 lines not shown]
Make swap encryption truly optional, rather than just able to be
default-disabled
- New option VMSWAP_ENCRYPTION (enabled by default in conf/std along with
VMSWAP)
- Remove the "aes" attribute from VMSWAP and hand it to VMSWAP_ENCRYPTION.
- Conditionalize all code and data related to swap encryption on the
new VMSWAP_ENCRYPTION option.
While the swap encryption code itself is not that large, it drags in
the AES code if enabled. If a constrained platform doesn't care about
encrypted swap, this lets it not pay the cost for AES.