Do not expect JSON output from TNC delete calls
This commit fixes a case where TNC's `DELETE /v1/systems/:id` endpoint returns 200 with an empty/non-JSON body, causing `unset_registration_details` to crash with `aiohttp.ContentTypeError` while attempting to decode the response as JSON. Passing `get_response=False` skips the body decode since the response payload is not used.
(cherry picked from commit 1ba1a484b5c216697e2ffb51dbf9fb585f5b0756)
[AMDGPU] Align GlobalISel with SelectionDAG for f16 to i1/i8 saturated conversions (#188019)
GlobaISel now also saturates `i1` and `i8` to `f16` conversion at `i16`
where available. As a side effect, this also causes the two uniform test
cases: `f16_i1` and `f16_i8` to use VALU instructions, instead of SALU
instructions. This is potentially sub-optimal but it makes it consistent
with ISel and has been already highlighted as future work in #187711.
[AMDGPU] AMDGPULibCalls: Set new intrinsic calling convention to C (#197364)
In #197151 libclc/test/math/fabs.cl,
tryReplaceLibcallWithSimpleIntrinsic replaces `call fastcc float
@_Z4fabsf` with `call fastcc float @llvm.fabs.f32`. But intrinsic call
must use CallingConv::C.
Revert "devel/pear-Console_CommandLine: Remove expired port"
There are some consumers which uses this port.
This reverts commit a1c02616d7a57a69f986b07f3f44fff7d117cdf2.
[RISCV][MC] add experimental `Zvvfmm` MC support (#196486)
This PR adds experimental MC layer support for the RISC-V `Zvvfmm` from
Integrated Matrix Extension based on the
[riscv-isa-release-fa55752-2026-05-04 spec
release](https://github.com/riscv/integrated-matrix-extension/releases/tag/riscv-isa-release-fa55752-2026-05-04).
As a follow up of `Zvvmm` in #193956
This PR:
- Renames `RISCVInstrInfoZvvmm.td` to `RISCVInstrInfoZvvm.td` so `Zvvmm`
and `Zvvfmm` share the same IME instruction file according to the spec.
And all future instructions from the `Zvvm family` will be placed here
too.
- Adds a new `VScaleReg` asm operand to support the `v0.scale` assembly
syntax.
- Adds assembler support for floating-point matrix instructions:
`vfmmacc.vv`, `vfwmmacc.vv`, `vfqmmacc.vv`, `vf8wmmacc.vv`
- Adds integer-input floating-point accumulate scaled instructions:
`vfwimmacc.vv`, `vfqimmacc.vv`, `vf8wimmacc.vv`
[3 lines not shown]
misc/py-posthog: Update 4.0.1 => 7.14.1, take maintainership
Changelog:
https://github.com/PostHog/posthog-python/blob/7.14.1/CHANGELOG.md
Improve port:
- Remove unnecessary DISTNAME because it's default value.
- Make a slight update to the Comment.
- Add additional WWW.
- Remove shebangfix because this port doesn't seem to install any
executable scripts.
- Update post-install-DOCS-on because it deals with no man pages.
PR: 295253
Sponsored by: UNIS Labs
interfaces: follow up on DHCP option sanitization
@sopex noted a) that two semicolons were missing which were likely
lost to a refactoring step and b) allowing "medi;a" to avoid the
sanity scan for option modifiers. To fix that second part we use
the normalization of interfaces_dhcp_safe() directly before returning
the parsed arguments to the caller. That way the result is clear
and easy to check.
PR: GHSA-5rx3-w735-74wm
(cherry picked from commit 9e7fad6c3188e148f5066e948cebba19f8682765)
devel/jujutsu: fix build with ports tree checked out by jujutsu
Fix issue reported in PR 295250:
My poudriere ports tree is a null mounted jj repo (git
colocated). Building docs fails, because it calls
jj util install-man-pages
which evidently tries to access
/usr/ports/.jj/repo/config-id
because it's being run from inside a jj repo.
There must not be a .jj directory in the directory were jj is
run or in any parent directory to prevent an error abort:
Internal error: Failed to determine the secure config for a repo
[6 lines not shown]
[OpenMP][offload] Inline target reductions (#196061)
Significantly reduces register usage and removes register spilling in
`offload/test/offloading/multiple-reductions.cpp`, for example. Provides
speedup of up to 5-10x for a lot of reductions in such a larger setup.
Based on https://github.com/llvm/llvm-project/pull/195940.
See also the discussion in
https://github.com/llvm/llvm-project/pull/195102.
interfaces: follow up on DHCP option sanitization
@sopex noted a) that two semicolons were missing which were likely
lost to a refactoring step and b) allowing "medi;a" to avoid the
sanity scan for option modifiers. To fix that second part we use
the normalization of interfaces_dhcp_safe() directly before returning
the parsed arguments to the caller. That way the result is clear
and easy to check.
PR: GHSA-5rx3-w735-74wm