arm64: Fix a MTE check
It should be for FEAT_MTE2 as the registers aren't implemented for
FEAT_MTE.
While here fix the style of the comment explaining the check.
Reported by: markj
Fixes: 58de79153622 ("arm64: mte: configure initial state for system registers")
Sponsored by: Arm Ltd
arm64: Support some per-thread sctlr_el1 fields
This will be used to enable MTE from userspace.
Sponsored by: Arm Ltd
Differential Revision: https://reviews.freebsd.org/D55950
NAS-140814 / 26.0.0-BETA.2 / Copy VM NVRAM and TPM state on clone (by Qubad786) (#18839)
## Context
In continuation of the changes made in
https://github.com/truenas/middleware/pull/18764, the same fixes have
been applied to the VM cloning process ensuring that when a VM is cloned
- relevant files are copied over of the VM as well so tpm/secure boot
function as intended.
Original PR: https://github.com/truenas/middleware/pull/18828
Co-authored-by: M. Rehan <mrehanlm93 at gmail.com>
[clang][Lex] Collapse relative extern module paths when recursing to prevent unbounded path length growth. (#193691)
Ref #147220.
### Problem Description
Bazel's use of clang modules for its `layering_check` emits `extern
module` declarations relative to some base path meaning those paths
usually include long sequences of `../` followed by the path to the
module itself.
When parsing `extern module` in the module file, we (I believe
intentionally) silently ignore missing module files. Currently in the
problem case if the file existence check failed for any _other_ reason
it also silently ignores it. This means that `-fmodules-strict-decluse`
that bazel uses for the layering_check can throw a spurious
`err_undeclared_use_of_module` error which is the problem reported in
#147220.
Clang's `extern module` parsing chooses to concatenate these relative
[17 lines not shown]
[flang][NFC] Converted five tests from old lowering to new lowering (part 53) (#194772)
Convert five tests to use new HLFIR lowering instead of legacy FIR
lowering:
Lower/allocatable-callee.f90, Lower/allocatable-caller.f90,
Lower/assignment.f90, Lower/assumed-shape-caller.f90,
Lower/Intrinsics/count.f90
[VPlan] Check FOR/FMinMaxNum epilogue restrictions in VPlan. (#191815)
Move checking of FOR/FMinMaxNum restriction checks for epilogue
vectorization to hasUnsupportedHeaderPhiRecipe and perform checks
directly on VPlan.
This unifies the checking code and enables epilogue vectorization of
VPlans with dead FORs, although the latter should be cleaned up by
scalar optimizations earlier in practice.
PR: https://github.com/llvm/llvm-project/pull/191815
[InstCombine] Fold select of ordered fcmps of fabs over NaN-scrubber selects to a single select (#192182)
Fold `select (fcmp <ordered> (fabs (select isKnownNeverNaN X, X, Y)),
K), ...` into a single compare/select directly on `X`. The outer fcmp is
limited to ordered predicates, since only they preserve the original
non-NaN behavior.
fixes #143649
alive2: https://alive2.llvm.org/ce/z/G8UmjY
Generalized proof (needs local alive2 build):
```alive2
declare double @llvm.fabs.f64(double)
define double @src(double %x, double %y, double %k) {
entry:
%ord = fcmp ord double %x, 0.000000e+00
[14 lines not shown]
[mlir][x86] Support for `f8` AMX tiled dot-product. (#194786)
This patch enable AMX tiled dot-product support for `f8E4M3FN` and
`f8E5M2` types in MLIR by lowering to below llvm instrincs:
- `llvm.x86.tdpbf8ps`
- `llvm.x86.tdpbhf8ps`
- `llvm.x86.tdphbf8ps`
- `llvm.x86.tdphf8ps`
[mlir][Presburger] Fix inlining failure for dynamicAPIntFromInt64 in debug builds (#194820)
When `dynamicAPIntFromInt64` is passed as a function pointer to
`llvm::transform`, it becomes an indirect call. This causes the compiler
to fail to inline the function despite the
`LLVM_ATTRIBUTE_ALWAYS_INLINE` annotation, resulting in a compilation
error in debug builds:
```
error: inlining failed in call to 'always_inline' 'llvm::DynamicAPInt llvm::dynamicAPIntFromInt64(int64_t)': indirect function call with a yet undetermined callee
250 | LLVM_ATTRIBUTE_ALWAYS_INLINE DynamicAPInt dynamicAPIntFromInt64(int64_t X) {
```
Fix this by wrapping `dynamicAPIntFromInt64` in a lambda, turning the
indirect call into a direct call that the compiler can inline at the
call site.
ports-mgmt/pkg: update to 2.7.5
Changes:
- backup lib: loudly complain if a library is not in filesystem but in plist
- backup lib: fix with rootdir
- progress: avoid useless newlines
- config: accept more boolean types
- fix fflags support
Services: Kea DHCPv6: infer IPv6 lease type in delete script via lease lookup so IA_NA and IA_PD can be deleted (#10231)
This avoids propagating lease type handling through controller and UI
layers while fixing unreliable deletion of IA_PD leases.
The approach is pragmatic: in the extremely unlikely case that IA_NA and
IA_PD share the same base address, multiple leases may be deleted. This
tradeoff is considered acceptable given the low impact and recoverable
nature of DHCP leases.
* Also expose type and iaid in the leases page for completion
* prevent truncating duid or iaid in default view
rpki-client: properly ignore missing unsupported files in -n mode
RFC 9286 section 6.5 mandates that we fetch all the files in a manifest
fileList and validate their hashes. By design, RRDP will ship all the
available files whereas in rsync we decided to fetch only the files of
types we explicitly support. While we check the hashes of unsupported
files, they won't be copied into the cache of validated files.
Since unsupported files are not in the validated cache and may or may
not be present in the temporary directory of fetched objects, there is
logic that ensures that the hashes of all available files are correct
and attempts to avoid an error for files absent from both directories.
Whether all the above decisions in both, standards and our code, are
fully sound is not entirely clear.
Be that as it may, Job observed that this logic was incorrect in noop mode
where no temporary directory is available. This resulted in rejecting the
one manifest that still lists a Ghostbuster's record (RFC 6493) and as a
[7 lines not shown]
