[EXPERIMENT] Implicitly attribute ALLOCATABLE/POINTER components as managed
Extend the implicit managed attribution in resolve-names to derived-type components, instead of selecting the allocator index at the ALLOCATE site.
[ORC] Resolve JITLoaderGDB alloc actions via lookupAndApply (#223325)
ELFDebugObjectPlugin resolved its RegisterJITLoaderGDB alloc-action
address with EPC.getBootstrapSymbols. For consistency, switch to
lookupAndApply/recordAddr on the bootstrap JITDylib instead.
NAS-143607 / 27.0.0-BETA.1 / Stop docker.socket before docker.service (#19697)
## Problem
`DockerService.stop()` stopped `docker.service` first and
`docker.socket` second, leaving the socket armed for the whole service
teardown — around 11.5 seconds on a box with a couple of dozen
containers. Anything connecting to `/var/run/docker.sock` in that window
socket-activates the very service we are stopping. With the
`StartLimitBurst=1` drop-in that phantom start gets refused, the unit
latches `failed`, and `CollectMode=inactive` never garbage-collects a
failed unit — so the rate-limit counter stays pinned and nothing short
of a reboot recovers. That is what leaves an apps-pool migration
reporting "Migration completed successfully" at 100% and `Docker service
is not running` in the same job.
## Solution
Enqueue the stop on `docker.socket` first. This is not really a
reordering of the teardown: systemd builds a two-job transaction and
still takes the service down first per `After=`. What changes is that a
[10 lines not shown]
[X86] Fix `"Cannot select"` for `bf16` vector selects on a scalar condition under `AVX10.2` (#222854)
Fixes #222673
A `select i1 %c, <8 x bfloat> %a, <8 x bfloat> %b` failed instruction
selection with `+avx10.2-512` on a `v8bf16 X86ISD::CMOV`. Selects on a
scalar condition are lowered to the `CMOV_VR*` pseudos and expanded to a
branch, but those pseudos only have patterns for integer and f16
vectors. Before #101603 bf16 vectors were treated as "soft" everywhere,
so `LowerSELECT` bitcast them to `v8i16` first and never produced a bf16
CMOV. That PR made bf16 non-soft under AVX10.2 to enable native
arithmetic, which silently removed the only bf16-aware path in
`LowerSELECT` without adding a replacement. `v16bf16` and `v32bf16` hit
the same thing.
`LowerSELECT` now takes the integer-bitcast path for every bf16 vector,
using the existing `isBF16orSoftF16` helper, so the select is lowered
exactly as it is on every other bf16 target and as `v8f16` is on FP16
targets. Scalar `bf16` is soft-promoted to `f32` before lowering, so it
[2 lines not shown]
[libc++] Move _LIBCPP_HAS_COND_CLOCKWAIT into condition_variable.h (#222904)
`_LIBCPP_HAS_COND_CLOCKWAIT` is only used inside
`<__condition_variable/condition_variable.h>`, so we might as well move
it there.
[libc++] Optimize string copy construction (#222021)
We know that the string size provided to `__init_copy_ctor_external` is
less than or equal to `max_size()`, so we don't need to do that check
again. Removing that check allows the compiler to ShrinkWrap the small
size path and also removes some unnecessary work in the allocating path.
[MLIR][OpenMP] DeclareTargetInterface and DeclareTargetAttr cleanup (#217295)
The changes introduced by this patch are intended to avoid triggering
multiple by name lookups to the "omp.declare_target" attribute every
time any data from the `DeclareTargetInterface` is queried, remove the
need for keeping multiple default values for the same data, clean up the
assembly format and generally improve the usage of the interface.
List of changes:
- `DeclareTargetInterface` only provides `setDeclareTarget` and
`getDeclareTarget` methods to handle the "omp.declare_target" attribute,
maintaining a single canonical way of accessing it.
- `DeclareTargetAttr` provides direct access to the capture clause and
device type enums, rather than wrapping them into an `Attribute`. These
are now mandatory as well. Both changes together make accessing them
more straightforward and simplify the attribute representation.
[libc++] Provide aligned allocation function iff the compiler claims support (#219199)
There isn't much of a point to providing declarations for aligned
allocation functions but not allowing the compiler to use them. So
either aligned allocations should be allowed to be used via
`-faligned-allocation` or not provided at all.
firewall: add private network exclusions to default IPv6 bogons (#10125)
Allows ULA and link-local access on new systems where
the bogons haven't been updated yet.
(cherry picked from commit 14ce4ca943630136194aaf8bd4e28bd562f91cff)
firewall: add private network exclusions to default IPv6 bogons (#10125)
Allows ULA and link-local access on new systems where
the bogons haven't been updated yet.
zino: update to version 2.5.2.
Pkgsrc changes:
* version-bump + checksums + minor adjust of dependencies.
Upstream changes:
- Added explanation section to documentation covering Zino's history,
core concepts, and technical architecture
([#435](https://github.com/Uninett/zino/issues/435)) - Added
documentation for cuRitz, with screenshots.
([#568](https://github.com/Uninett/zino/issues/568))
- `--user` and the `process.user` setting now accept a numeric
`UID` or `UID:GID` or, as previously, a user name, so Zino can drop
privileges to a UID that has no entry in `/etc/passwd` (e.g. inside
a container)
- BGP sessions that go down are reported again. On routers that
send Zino an SNMP trap when a session drops, the drop was only
[16 lines not shown]