Use truenas-discovery service
This commit replaces avahi, wsdd, and netbios services with a
unified truenas-discovery service. This simplifies the middleware
implementation of these services. Tests are adjusted so that we
have more direct testing that middleware configuration changes
are reflected in the in-memory running configuration of the
truenas-discoveryd daemon. During testing / validation I
discovered that there were some escape avenues whereby the
configuration may not be properly reloaded after netbios name
or workgroup changes.
[mlir][tosa] Fix integer bilinear (quantized) tosa.resize lowering to use floordivsi (#193821)
## Background
`tosa.resize` in bilinear integer (quantized) mode lowers to a
`linalg.generic`
body that, for each output pixel, computes a corresponding input
coordinate and
blends the four neighboring input pixels. The mapping is:
```
val = out_coord * scale_d + offset
index = val / scale_n // integer part — which input pixel to start from
delta = val - index * scale_n // fractional part, scaled to [0, scale_n)
```
`delta` is the interpolation weight toward the next pixel. The bilinear
formula
(integer path) is:
[133 lines not shown]
[flang][NFC] Converted five tests from old lowering to new lowering (part 47) (#193886)
Tests converted from test/Lower: namelist-common-block.f90,
nested-where.f90, nullify.f90,
OpenMP/Todo/omp-default-clause-inner-loop.f90, optional-value-caller.f90
[lldb-dap] extend env when testing reverse request (#193743)
When testing lldb-dap's "runInTerminal" mode, the `"env"` argument is
meant to extend/override the current environment, not replace it.
This causes issues on Windows when Python is not in the System's Path.
The reverse request fails because lldb-dap can't find Python.
[AArch64][llvm] Generate asm parser extension map from TableGen (NFC)
Modify ARMTargetDefEmitter to emit the assembly parser `ExtensionMap[]`
and replace the hand-written table in AArch64AsmParser.cpp with the
generated one.
Keep the assembly parser-only quirks in the emitter: the directive
denylist, the legacy primary spellings for `mte` and `compnum`, and the
extra bits needed for the `sve2-*` shorthand extensions.
This removes the duplicate manual table while preserving existing
directive parsing and required-feature diagnostics.
[AArch64][clang] Fix typos in `arm_sve.td` (NFC) (#192981)
Rename some typos in `arm_sve.td`, rather than perpetuate them (since
I'll be adding more MMLA intrinsics shortly).
No functional change.
devel/electron39: Fix build with rust 1.94
The previous patch fixed builds with rust 1.95. However, it broke
builds with rust 1.94, which is the current version in the ports
tree. This commit makes it build with both rust 1.94 and 1.95.
Fixes: 9cffc4aeae6a (devel/electron39: Fix build with rust 1.95)
devel/electron38: Fix build with rust 1.94
The previous patch fixed builds with rust 1.95. However, it broke
builds with rust 1.94, which is the current version in the ports
tree. This commit makes it build with both rust 1.94 and 1.95.
Fixes: 058c1391b4f5 (devel/electron38: Fix build with rust 1.95)
devel/electron40: Fix build with rust 1.94
The previous patch fixed builds with rust 1.95. However, it broke
builds with rust 1.94, which is the current version in the ports
tree. This commit makes it build with both rust 1.94 and 1.95.
Fixes: 5c791a04ff9e (devel/electron40: Fix build with rust 1.95)
devel/electron37: Fix build with rust 1.94
The previous patch fixed builds with rust 1.95. However, it broke
builds with rust 1.94, which is the current version in the ports
tree. This commit makes it build with both rust 1.94 and 1.95.
Fixes: bb65949e4aae (devel/electron37: Fix build with rust 1.95)
Fix previous; the old cpuspeed was in MHz by the end of cpu_startup(),
not MHz*10 (despite being MHz*10 earlier in startup).
Also, don't const-fold by hand; let the compiler do it so that it's
more obvious what is going on.
[lldb][Linux] Add overlay and effective permissions to "memory region" (#184115)
In this change I'm extending the "memory region" command to show users
the
overlay permissions that a protection key refers to, and the result of
applying that overlay to the page table permissions.
For example, protection key 0 refers to Perm0 in the por register.
```
(lldb) register read por
Perm0 = Read, Write, Execute
```
This is the default key, so many regions use it.
```
(lldb) memory region --all
<...>
[0x000ffffff7db0000-0x000ffffff7f40000) r-x /usr/lib/aarch64-linux-gnu/libc.so.6 PT_LOAD[0]
protection key: 0 (rwx, effective: r-x)
```
[30 lines not shown]
