[X86] Allow EVEX compression for VPMOV*2M + KMOV pattern (#175219)
This patch extends the X86CompressEVEX pass to recognize and compress
multi-instruction masking patterns. It also adds relevant tests for the
new pattern.
Fixes #171746
Fixes #174871
[InstCombine][X86] Move simplifyX86FPMaxMin handling from simplifyDemandedVectorEltsIntrinsic to instCombineIntrinsic (#175441)
My fault for missing this when reviewing #174806 - technically we might
benefit from demanded elts handling for these intrinsics some day, but
the base implementation should be in instCombineIntrinsic
Noticed while reviewing #175375 which I recommended reuses more of the
simplifyX86FPMaxMin handling.
py-X: updated to 0.17
0.17 (2025/11/02):
- Move metadata from setup.py to pyproject.toml
- graph modules:
- enable log axis on negative values (either all values need to be positive
or negative)
- move the density parameter to the rater (with a deprecation warning in
the axis)
- limit subaxis range in bar and split axes to [0..1] except for epsilon=None
- improve exception handling for invalid data in density style
- add a new grid layer below filldata and paint axes grids there
- support modification of x2, y2, etc. graph axes by keyword arguments
- Cleanup of pdfwriter and pdfextras
- Add support for fillattrs and trafos in UnicodeEngine
- various improvements to the documentation
0.16 (2022/10/16):
- graph module:
[24 lines not shown]
NAS-139243 / 25.10.2 / Use recursive deletion for Docker dataset during restore (by sonicaj) (#17997)
Automatic cherry-pick failed. Please resolve conflicts by running:
git reset --hard HEAD~1
git cherry-pick -x 9e43f9afcd22e906ffcdd2b1d7e61d5f00f96023
If the original PR was merged via a squash, you can just cherry-pick the
squashed commit:
git reset --hard HEAD~1
git cherry-pick -x 3013219f451a900841fa0e80ff62477cbbfe3dc7
This commit adds recursive flag when destroying the Docker dataset
during backup restore, ensuring child datasets and snapshots are
properly removed.
Original PR: https://github.com/truenas/middleware/pull/17988
Co-authored-by: Waqar Ahmed <waqarahmedjoyia at live.com>
emulators/virtualbox-ose{,-legacy}: Limit python to 3.10-3.11
This is temporary workaround for build error:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.50/src/libs/xpcom18a4/python/src/VariantUtils.cpp:197:7: error: use of undeclared identifier 'PyUnicode_GET_SIZE'; did you mean 'PyDict_GET_SIZE'?
if (PyUnicode_GET_SIZE(val_use) == 0) {
^~~~~~~~~~~~~~~~~~
PyDict_GET_SIZE
/usr/local/include/python3.12/cpython/dictobject.h:53:26: note: 'PyDict_GET_SIZE' declared here
static inline Py_ssize_t PyDict_GET_SIZE(PyObject *op) {
^
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.50/src/libs/xpcom18a4/python/src/VariantUtils.cpp:501:38: error: use of undeclared identifier 'PyUnicode_AS_UNICODE'
FILL_SIMPLE_POINTER( PRUnichar, *PyUnicode_AS_UNICODE(val_use) );
^
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.50/src/libs/xpcom18a4/python/src/VariantUtils.cpp:829:8: error: use of undeclared identifier 'PyUnicode_GetSize'
if (PyUnicode_GetSize(ob) == 0) {
^
Support for the python 3.12+ was added in the VirtualBox 7.0.
[3 lines not shown]
asmc(4): Stop building it on i386, as it supports only 64-bit chipsets
Reported by: ngie
Fixes: fde9fe18219f ("i386: Fix kernel compilation after introduction of ASMC_DEBUG option")
Sponsored by: The FreeBSD Foundation
sys: vt_efifb: EFI not supported on i386; move it back to amd64/NOTES
We do not support EFI boot on i386. Thus:
1. Move (back) 'device vt_efifb' from x86/NOTES to amd64/NOTES.
2. Remove 'device vt_efifb' from i386/MINIMAL.
Reported by: jhb
Fixes: f224591746bd ("Add ASMC_DEBUG make option")
Fixes: 67599eef01f5 ("sys/x86/NOTES: Add vt_efifb")
Sponsored by: The FreeBSD Foundation
[lldb] Fix TestFrameVarDILCast.py build on Windows AArch64
This patch adds <cstddef> to main.cpp in TestFrameVarDILCast.py so that
std::nullptr_t is properly declared. It fixes the TestFrameVarDILCast.py
compile failure observed on the LLDB Windows AArch64 buildbot:
https://lab.llvm.org/buildbot/#/builders/141
The issue was introduced by commit 539cf92 in #170332.
dpkg: updated to 1.23.3
dpkg (1.23.3) unstable; urgency=medium
[ Guillem Jover ]
* Perl modules:
- Dpkg::Vendor::Debian: Mask PIE on m68k, sh4 and x32.
Thanks to Adrian Bunk <bunk at debian.org>.
- Dpkg::Version: Add new has_epoch() and has_revision() methods.
- Dpkg::Source::Package::V1: Make debian/rules executable on extract if
present.
dpkg (1.23.2) unstable; urgency=medium
[ Guillem Jover ]
* Perl modules:
- Dpkg::BuildProfiles: Add workaround for callers passing invalid formulas.
Diagnosed by Chris Hofstaedtler <zeha at debian.org>.
[11 lines not shown]
interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
[LLDB] Increase level of headings in lldb-dap docs (#175519)
The lldb-dap docs had more than one top-level heading (one `#`). All top
level headings are shown in the "Using LLDB" list on the left side. In
this case, "Supported Features" and "Configuration Settings Reference"
showed up there.
With this PR, these headings are increased by one level. This also
increases the level of "Debug Console" (child of "Supported Features")
and "Common/Launch/Attach configurations" (child of "Configuration
Settings Reference").
router advertisements: migrate to MVC/API (#9603)
Migrate router advertisements to its own space. Although
the data shifts around a bit the end result should be equivalent.
Of note is that we currently do not have visibility for automatic
interface tracking when not disabled, but they can be disabled
manually by adding the interface configuration and unchecking
the service enable.
Co-authored-by: Monviech <gitacc at pischem.com>
textproc/television: update to 0.14.5
0.14.5 - 2026-01-10
⛰️ Features
250e7ac (preview) Add word wrapping to the preview panel by @xosxos in #849
d6553e7 (preview) Accept Braille Unicode characters by @xosxos in #848
e338cbe (tldr) Colored tldr preview by @alexpasmantier
🚜 Refactor
0bd20fc (nix) Flake using flake-parts, crane, and rust-overlay by @doprz in #846
📚 Documentation
35243a4 (cable) Update channel documentation (auto) by @github-actions[bot] in #845
c25f721 (cli) Update tv --help output (auto) by @github-actions[bot] in #850
⚙️ Miscellaneous Tasks
[30 lines not shown]
[AMDGPU][SIInsertWaitcnt] Implement Waitcnt Expansion for Profiling (#169345)
Reference issue: https://github.com/ROCm/llvm-project/issues/67
This patch adds support for expanding s_waitcnt instructions into
sequences with decreasing counter values, enabling PC-sampling profilers
to identify which specific memory operation is causing a stall.
This is controlled via:
Clang flag: -mamdgpu-expand-waitcnt-profiling /
-mno-amdgpu-expand-waitcnt-profiling
Function attribute: "amdgpu-expand-waitcnt-profiling"
When enabled, instead of emitting a single waitcnt, the pass generates a
sequence that waits for each outstanding operation individually. For
example, if there are 5 outstanding memory operations and the target is
to wait until 2 remain:
[23 lines not shown]
devel/cargo-nextest: update to 0.9.120
Added
Support for using a pager like less with nextest's output. Currently supported are:
cargo nextest list
cargo nextest show-config test-groups
-h and --help commands
The pager support is closely modeled after the Jujutsu version control system. The default pager is less -FRX on Unix platforms, and a builtin pager (based on sapling-streampager) on Windows.
cargo nextest self update now supports --beta and --rc flags to update to prerelease versions.
Revert "[Clang] Warn when `std::atomic_thread_fence` is used with `fsanitize=thread`" (#175520)
Reverts llvm/llvm-project#166542
It caused clang to assert with: `!isa<CXXDestructorDecl>(D) && "Use
other ctor with dtor decls!"`
see comment on the PR.
