[CIR][OpenMP] Add emitDeclTargetVarDeclLValue for global variable access (#234075)
Limit the global access NYI to declare target variables that need
indirect access on the device
---------
Co-authored-by: Steffen Larsen <sholstla at amd.com>
Revert "[AArch64] Make all fixed-width masked loads/stores legal on SVE targets (#232757)" (#238371)
This reverts commit eeb1dbff9d9871a178d2608c4e0d6486422f14b1.
I believe the PR itself is functionally correct, but it exposed a
pre-existing bug in the backend which caused post-commit buildbot
failures. Reverting for now so that I can post the backend fix first.
security/pkcs11-provider: Fix build with base openssl.
Just arrange to install modules into $PREFIX/lib/ossl-modules for
base openssl; it is the user's responsibility to set OPENSSL_MODULES
or pass -provider-path or otherwise configure base openssl to use
pkgsrc modules.
No change to build with pkgsrc openssl, and this didn't build with
base openssl before, so no revbump.
Time out LDAP requests when the server does not reply
LDAPClient did not limit the wait for an LDAP reply. search() called
result3() with no timeout, and the code did not set OPT_TIMEOUT. If the
server became unreachable while the connection was open, the health
check search waited until the kernel closed the TCP connection. With
the default tcp_retries2, this takes approximately 15 minutes. In the
reported test, the directory service status stayed HEALTHY for 24
minutes after the LDAP server became unreachable.
The code also set OPT_NETWORK_TIMEOUT with the global set_option()
after initialize(). initialize() copies the global options to the
handle, so the first handle did not get this timeout.
- Set OPT_NETWORK_TIMEOUT and OPT_TIMEOUT on the handle. OPT_TIMEOUT is
the default maximum time to wait for a reply. The bind and StartTLS
calls use only this default.
- Give the timeout to result3() in search(). The search_ext() timeout
is only a time limit for the server.
[6 lines not shown]
Format test_ldap_client.py with ruff
Apply ruff format with src/middlewared/pyproject.toml, as the ruff CI
job does for new files. The change is formatting only.
(cherry picked from commit c7d96e4a368d4564d8d8e7967c33d9a25666e498)
NAS-143750 / 28.0.0-BETA.1 / Time out LDAP requests when the server does not reply (#20117)
LDAPClient did not limit the wait for an LDAP reply. search() called
result3() with no timeout, and the code did not set OPT_TIMEOUT. If the
server became unreachable while the connection was open, the health
check search waited until the kernel closed the TCP connection. With the
default tcp_retries2, this takes approximately 15 minutes. In the
reported test, the directory service status stayed HEALTHY for 24
minutes after the LDAP server became unreachable.
The code also set OPT_NETWORK_TIMEOUT with the global set_option() after
initialize(). initialize() copies the global options to the handle, so
the first handle did not get this timeout.
- Set OPT_NETWORK_TIMEOUT and OPT_TIMEOUT on the handle. OPT_TIMEOUT is
the default maximum time to wait for a reply. The bind and StartTLS
calls use only this default.
- Give the timeout to result3() in search(). The search_ext() timeout is
only a time limit for the server.
[3 lines not shown]
security/netbird: Update 0.81.5 => 0.82.0
This release removes MySQL store and deprecates Rosenpass,
please see pkg-message or the changelog for more details.
Changelog:
https://github.com/netbirdio/netbird/releases/tag/v0.82.0
PR: 300474
Approved by: osa, vvd (mentors, implicit)
MFH: 2026Q4
hwpmc/amd: prime UMC perfmon block before programming counter registers
UMC counter register writes do not take effect while no counter in the
channel is enabled. Reserve the last counter slot of each UMC channel
and keep it enabled with EventSelect=0 so writes to the remaining slots
take effect. Reserved slots are not exposed to MI code.
UMC perfmon MSRs are package-scoped. A per-socket reference count arms
the reserved slots on the first amd_pcpu_init() for a socket and
disarms them on the last amd_pcpu_fini().
Reviewed by: mhorne
Sponsored by: AMD
Signed-off-by: Osvaldo Janeri Filho <ojanerif at amd.com>
Pull Request: https://github.com/freebsd/freebsd-src/pull/2422
[SystemZ][z/OS] Add a ForceUTF8 to OpenFlags to open tablegen files as UTF-8 on z/OS (#235887)
This patch adds a OF_ForceUTF8 to OpenFlags which is turned on when
creating TableGen files in UTF-8
In this PR https://github.com/llvm/llvm-project/pull/235035, the
solution of tagging a file as UTF-8 after opening did not work and we
still get IBM-1047 tagged files (see same failure here
https://lab.llvm.org/staging/#/builders/237/builds/1110). I did some
analysis with IBM Bob and came to the following conclusion:
`A second F_SETTAG is ignored on a file opened with O_TRUNC. It works on
a file opened without O_TRUNC (for example O_CREAT|O_EXCL).
Auto-conversion state makes no difference.`
[MLIR][SCF] Include IndexSwitchOp in scf.yield aliasing (#236644)
The bufferization interface for `scf.yield` only recognized `scf::IfOp`
and `scf::ExecuteRegionOp` as parents. A value yielded from
`scf.index_switch` therefore had no alias relation with the switch
result, so one-shot bufferization could write through a non-writable
input in place.
The same model's `bufferize()` already lists `scf::IndexSwitchOp`, so
this adds it on the aliasing side as well. `isWritable` and
`bufferizesToMemoryWrite` need no change: the switch result is an
`OpResult`, and the switch itself does not write memory.
Tests: alias-set coverage for single- and multi-result switches in
`one-shot-bufferize-analysis.mlir`, plus an end-to-end case in
`one-shot-bufferize.mlir` that now materializes a `memref.alloc` before
the write instead of writing into the input buffer.
Fixes #236567.
Assisted-by: Claude Code
