[flang][FIRToMemRef] Fix lowering of complex array component slices (z%re, z%im) (#191846)
fir.slice with a path component (z%re, z%im) was silently dropped by
FIRToMemRef. Since memref.reinterpret_cast cannot change element type,
layout must come from the projected box descriptor via
fir.box_dims/fir.box_elesize rather than the triplets. Only
complex-array projections are handled here —
sizeof(complex<T>)/sizeof(T) = 2 is always exact for divsi. Derived-type
component projections bail out to downstream FIR-to-LLVM lowering where
strides can be non-integer.
[flang][NFC] Converted five tests from old lowering to new lowering (part 44) (#191926)
Tests converted from test/Lower/Intrinsics: verify.f90
Tests converted from test/Lower: io-char-array.f90,
io-implied-do-fixes.f90, io-item-list.f90, io-statement-1.f90
Run clang-format on TargetParser/Triple.{cpp,h} (#192064)
It already got inconsistent because new changes require complying with
clang-format on CI, while everything old is not complying with it.
[TargetLowering] Prevent expandVectorFindLastActive from creating illegal vector types during vector op legalization. (#190914)
This code needs to create a step vector but we only have a mask vector
type. If the step vector is too large it might not be an MVT. This
causes the getSimpleVT() call for getTypeAction to fail. We can replace
that with the EVT version of getTypeAction, but we'll still fail trying
to legalize the vselect. The getOperationAction query will return Expand
for non-simple VTs. ExpandVSELECT will try to unroll the vselect which
will fail for scalable vectors. We could hack that to not unroll
scalable vectors, but that would be a hack.
To fix this, split the FIND_LAST_ACTIVE into two if the step vector
needs to be split. Those will recursively legalize and eventually arrive
at a size we can create a valid step vector for.
One existing test changes because it created an illegal type which
happened to still be an MVT. This allowed getOperationAction to return
Legal, even though the type isn't legal.
[2 lines not shown]
[OpenMP][OMPT] Revert `control_tool.c` changes from #191429 (#192069)
On s390x, the changes to `control_tool.c` cause a different return
address to be returned from the call to `print_current_address(0)`. Due
to the strictness of the current address returned by this call, this
lead to a test failure.
Since the return values of `omp_control_tool` are checked in separate
tests already, revert the changes to ensure that the return address
stays at the expected value.
Signed-off-by: Jan André Reuter <j.reuter at fz-juelich.de>
[TableGen] Fix the non-determinism in DFAPacketizerEmitter.cpp (#192037)
Sort the std::set ProcItinList by Record name, not the pointer address.
---------
Co-authored-by: Bao, Qiaojin (Fred) <Qiaojin.Bao at amd.com>
[AArch64] C1-Ultra Scheduling model (#182251)
This patch adds the C1-Ultra scheduling model. This model is largely
based on the Neoverse V3 scheduling model with appropriate changes made
based on information available in the software optimization guide for
this core.
https://developer.arm.com/documentation/111079/3-0
[AArch64][TTI] Increase cost for masked memory operations requiring splitting (#191417)
If we need to split the memory operation, we'll also need to split the
mask.
This has a performance benefit in some cases when the loop vectorizer is
asked to maximize bandwidth and ends up choosing a VF that's too high
when tail folding. The costs of splitting the masks are not accounted
for in the current model, so this is something of a brute-force approach
to avoiding the wider VFs.
sysutils/ansible: Fix ansible.posix.mount - core 2.19 deprecation warning
Fix:
[WARNING]: Deprecation warnings can be disabled by setting `deprecation_warnings=False` in ansible.cfg.
[DEPRECATION WARNING]: Passing `warnings` to `exit_json` or `fail_json` is deprecated. This feature will be removed from ansible-core version 2.23. Use `AnsibleModule.warn` instead.
ansible-collections/ansible.posix Issue #676 describes the issue above.
See https://github.com/ansible-collections/ansible.posix/issues/676.
Upstream commit ab8dfef from pull upstream request #670 addresses this bug.
See https://github.com/ansible-collections/ansible.posix/pull/670.
We cherry-pick the upstream pull request here to remove the annoying
message.
Fixes: 2bf152f274d4
www/freenginx: update third-party njs module: 0.9.4 -> 0.9.6
Bump PKGREVISION.
Sponsored by: tipi.work
<ChangeLog>
Changes with njs 0.9.6 03 Mar 2026
nginx modules:
*) Bugfix: fixed expire field truncation in shared dict state files.
Millisecond timestamps were silently truncated to 10 digits,
making restored entries appear expired on restart.
The issue has been present since eca03622 (0.9.1).
*) Bugfix: suppressed slab log_nomem for evict shared dict zones.
When evict is enabled, memory allocation failures are expected
and handled by evicting old entries.
[87 lines not shown]
www/freenginx-devel: update from 1.29.6 to 1.29.7
Sponsored by: tipi.work
<ChangeLog>
*) Feature: OpenSSL 4.0 compatibility.
*) Bugfix: a segmentation fault might occur in a worker process if the
ngx_http_dav_module was used to handle COPY and MOVE methods in a
location with the "alias" directive.
*) Bugfix: client host name was not escaped in requests to the
authentication server and in the XCLIENT command if the "resolver"
directive was used in the SMTP proxy.
*) Bugfix: in the mail proxy module.
</ChangeLog>
