[GOFF] Add emission of debug sections
This PR adds the definition of the debug sections for emission into
GOFF files. Currently, there is no debugger available which supports
all the sections. However, they all must defined to avoid regression
in LIT test cases.
Revert "[RISCV] Support RISCV BitInt larger than 128 (#175515)" (#178311)
This reverts commit e3156c531da5aa4ec604605ed4e19638879d773c.
We need to resolve a crash on trunk and LLVM 22. Reverting makes it
easier to backport.
Fixes #176637.
[lldb][SymbolFileDWARF][NFC] Call base class implementation of GetTypeSystemForLanguage (#178667)
Removes duplicated code by simply calling into the base-class.
Motivation is just that I stumbled upon this when making changes in the
surrounding area.
[X86] Canonicalise insertps(insertps(v,s,c0),s,c1) patterns to blend(v,splat(s)) (#178649)
Avoid situations where SimplifyDemandedVectorElts / shuffle combining
keeps messing with the zero masks of inner insertps - usually this is
benign but if they share operands it can cause infinite loops
Fixes #178538
Fix insert DBG_VALUE after terminator Failure for Hexagon (#173401)
This patch fixes an assertion failure on VLIW targets like Hexagon,
where a packet can contain both a terminator and a spill/copy. The
existing code did not look inside bundles, hence, it could leave a
transfer anchored on a terminator. When LiveDebugValues later
attempted to insert a DBG_VALUE after that packet, it hit:
Assertion `!TR.TransferInst->isTerminator() && "Cannot insert
DBG_VALUE after terminator"' failed
The change switches to instr_iterator and walks each packet with
getBundleStart/getBundleEnd. Packets containing a terminator are skipped
for insertion; non‑terminator ops in other packets are still processed
normally. This avoids illegal insertion points while keeping spill/copy
tracking intact.
[AMDGPU] Ensure v_mfma_scale_f32_{16x16x128|32x32x64}_f8f6f4 instructions are convergent (#178627)
The scaled variants of mfma instructions are not properly marked as
"convergent" and hence the machine-sink pass sinks them which is
incorrect.
This patch ensures that the instructions get marked as "convergent". The
new test also covers other mfma variants, but only the scale variants
are mistreated without the changes from this patch.
uvm_wait() was waking the pagedaemon then going to sleep on &uvmexp.free,
but made no indicator in a variable that the pagedaemon should do anything.
So, if the pagedaemon didn't see sleepin pmemrange allocations at the same
time, it would go back to sleep. This resulted in uvm_wait() wakeups
being substantially deferred.
ok beck claudio
NAS-139530 / 26.0.0-BETA.1 / Move dnsmasq dir to boot drive (#18118)
Placing it on the system dataset prevents unmounting during system
dataset migration.
[clang-tools-extra][docs] Add documentation for clang-reorder-fields (#178446)
Add comprehensive documentation for the clang-reorder-fields tool,
addressing #35520. The tool has existed in the repository but was
previously undocumented.
The documentation includes:
- Basic usage examples for C and C++ structs/classes
- Constructor initializer list reordering
- Designated initializer support (C++20)
- Detailed limitations and caveats
- Command line option reference
- Common use cases (memory layout optimization, etc.)
Fixes #35520
---------
Co-authored-by: EugeneZelenko <eugene.zelenko at gmail.com>
NAS-139344 / 26.0.0-BETA.1 / Maintain replication task state for disabled tasks (#18114)
This PR fixes a bug where disabling a replication task incorrectly
clears all execution history, causing "Last Run" to show "never" and
"Last Snapshot Sent" to show "No snapshots sent yet".
# Root Cause
When a replication task was disabled, zettarepl's state management
would:
*Remove the task from its active runtime state (self.state)
*The task would no longer appear in _known_tasks_ids()
*State queries would return no information for the disabled task
*Users lost all visibility into when the task last ran and what was last
replicated
# Behavior Changes
**Before:**
[9 lines not shown]
[lldb-dap] Conditionally check UBSan stack trace on Darwin only (#178655)
non-darwin platforms may have incorrect stop information location
heuristics. Enable assertion once UBSan stopInfo heuristic is updated.
I hit this locally, I don't see it hitting any CI bot but should, Mostly
likely the CI linux bots may not have `compiler_rt` run time enabled.
see
https://github.com/llvm/llvm-project/pull/177964#discussion_r2732271531
