[lldb] Make "help format" test more strict (#178216)
Originally added in a81bd7f1014f316b42bf7274f76a340b833e663b /
https://reviews.llvm.org/D35525, this test either was not strict enough,
or lldb's behaviour has drifted since.
I think the intention was to check exactly when the output of "help
format" would wrap. Which should happen when we have printed up to the
terminal width, minus a few characters because we walk backwards to the
closest whitespace point to break at (so we don't split a word).
I've updated the test to check the exact outputs and cover printing one
line and two instances where we need to split different amounts onto a
second line.
[SystemZ] Enable -fpatchable-function-entry=M,N (#178191)
This PR enables the option `-fpatchable-function-entry` for SystemZ. It
utilizes existing common code and just adds the emission of nops after
the function label in the backend.
SystemZ provides multiple nop options of varying length, making the
semantics of this option somewhat ambiguous. In order to align with what
`gcc` does with that same option, we#re choosing `nopr` as the
canoonical nop for this purpose.
For test, this adapts an existing test file from aarch64.
gnupg2: update to 2.5.17.
Despite the odd minor, 2.5 is the stable branch.
This update also renames the binary from gpg2 to gpg (the corresponding
configure option was removed).
Comment out some now hopefully unnecessary LDFLAGS.${OPSYS}.
Noteworthy changes in version 2.5.17 (2026-01-27)
-------------------------------------------------
* agent: Fix stack buffer overflow when using gpgsm and KEM. This
was introduced with 2.5.13; see the advisory. [T8044]
* tpm: Fix possible buffer overflow in PKDECRYPT. [T8045]
* gpg: Fix possible NULL-deref with overlong signature packets.
[T8049]
[571 lines not shown]
[Mips] Add r5900 (PlayStation 2 Emotion Engine) CPU support (#176666)
This PR adds basic support for the MIPS R5900 CPU, the Emotion Engine
processor used in the PlayStation 2.
**LLVM changes:**
- Add r5900 CPU definition (with soft float support for now)
- Disable instructions not supported by r5900 (64-bit multiply/divide,
LL/SC atomics, COP3)
- Add r5900 specific short loop delay slot fix (hardware errata
workaround)
- Set ISA extension `AFL_EXT_5900` in ELF flags for proper ABI
identification
**Clang changes:**
- Add r5900 as a valid CPU target for `-mcpu=r5900`
- Add r5900 to CPU test coverage
[Clang] prevent assertion in __has_embed parameter recovery at end-of-directive (#175104)
Fixes #175088
---
This PR addresses an assertion failure in the preprocessor triggered
when `__has_embed` parameter parsing reaches end-of-directive while
expecting a parenthesized argument.
[RISCV] Run combineOrToBitfieldInsert after DAG legalize (#177830)
Not combing `OR` into `QC.INSB(I)` before DAG legalization helps known
bits analysis to simplify the code if possible.
(cherry picked from commit 3ed48305ab19bf0090d2ca714a37dd7b0667b6c2)
[ARM] Count register copies when estimating function size (#175763)
`EstimateFunctionSizeInBytes`, in `ARMFrameLowering.cpp`, provides an
early estimate of the compiled size of a function, in a context that
wants to overestimate rather than underestimate.
In some cases it was underestimating severely, by over 20%. The
discrepancy was entirely accounted for by the fact that `COPY`
operations were not being counted at all, even though each one (or at
least each one that survives any post-regalloc optimizations) takes 2
bytes in Thumb or 4 in Arm. This could lead to a compile failure, if the
underestimated function size led frame lowering to not stack LR, but
later, `ARMConstantIslandsPass` needed to insert an intra-function
branch long enough to require a `bl` instruction, needing LR to have
been stacked.
The result of `EstimateFunctionSizeInBytes` was not directly available
for testing, so I added an `LLVM_DEBUG` at the end of the function. That
way, the test file doesn't need to try to make a >2048 byte function
[11 lines not shown]
gnupg: install binaries with '1' suffix
update DESCR to note that this is the old, unsupported version
Remove readline option since readline/bl3.mk is included unconditionally
in the Makefile anyway.
Clean some pkglint.
Bump PKGREVISION.
[WebAssembly] Zero and NaN checks for min/max (#177968)
Custom lower FMINNUM, FMINIMUMNUM, FMAXNUM and FMAXIMUMNUM to generate
relaxed_min and relaxed_max when the inputs cannot be NaN or signed
zero.
Tablegen patterns have also been modified to check the above conditions
when trying to match relaxed min/max using the pmin/pmax pattern.
[Clang] Fix rewrite-includes-bom.c to use POSIX-compliant regex (#176043)
As `\s` is a GNU extension, it is not supported by the system grep on
AIX and thus fails in the
[buildbot](https://lab.llvm.org/buildbot/#/builders/64/builds/6835):
```
******************** TEST 'Clang :: Frontend/rewrite-includes-bom.c' FAILED ********************
Exit Code: 1
Command Output (stdout):
--
# RUN: at line 1
cat /home/llvm/llvm-external-buildbots/workers/aix-ppc64/clang-ppc64-aix/llvm-project/clang/test/Frontend/Inputs/rewrite-includes-bom.h | od -t x1 | grep -q 'ef\s*bb\s*bf'
# executed command: cat /home/llvm/llvm-external-buildbots/workers/aix-ppc64/clang-ppc64-aix/llvm-project/clang/test/Frontend/Inputs/rewrite-includes-bom.h
# executed command: od -t x1
# executed command: grep -q 'ef\s*bb\s*bf'
# note: command had no output on stdout or stderr
# error: command failed with exit status: 1
--
[8 lines not shown]
[RISCV] Add tests for rv32 gather/scatter costs. NFC
There's a divergence with the rv32 costs that I plan on fixing in
another patch, so this precommits the tests for them.
The zve32f RUN lines were split off into another file so the check prefixes
are easier to reason about.
The -riscv-v-vector-bits-max RUN lines were also removed to simplify the
check prefixes since I'm not sure if they were intentionally testing any
specific logic.
(cherry picked from commit 3ad6d350c44f54482a86a7eb488732093eaed372)
[RISCV] Fix i64 gather/scatter cost on rv32 (#176105)
Fixes #175909
We compute the cost of a gather/scatter by multiplying the cost of the
scalar element type memory op by the estimated number of elements. On
rv32 though a scalar i64 load costs 2, even if we have zve64x.
This causes the cost to diverge between a vector of f64 and vector of
i64, even though both are the same. This fixes it by just using
TTI::TCC_Basic as the scalar memory op cost. The element type is checked
to be legal at this point.
I think we have the same issue for the strided op cost, but we don't
have test coverage for it yet.
(cherry picked from commit 0c1257cd46456513016b106d964dc5ad47c6289b)
textproc/rumdl: update to 0.1.2
[0.1.2] - 2026-01-27
Fixed
LSP: Only auto-fix on manual saves, not autosave (#340)
Prevents unwanted fixes when VS Code autosaves in the background
Auto-fix now only triggers on explicit Cmd+S / Ctrl+S saves
MD032: Add auto-fix for lazy continuation lines (#342)
When allow-lazy-continuation = false, lazy continuation lines now get proper indentation
Detects all inline formatting at line start (emphasis, strong, strikethrough, links, images, code)
Handles nested lists, blockquotes, and nested blockquotes correctly
MD037: Fix range calculation for emphasis spacing (#343) (thanks @kachick)
Fix ranges are now stored as absolute positions, preventing double-adjustment in fix mode
Added
[35 lines not shown]
editors/feathernotes: update to 1.4.0
This release includes two main changes:
- The password protection is made stronger. Of course that is done in a backward compatible way, i.e., all old password-protected documents of FeatherNotes can be opened like before.
- Since Qt6 refuses to open XML docs with "C0 control characters" in them (due to a backward incompatible change in Qt), all such characters are removed if encountered. Although control characters are rare and may enter a document only by being copied from outside sources, there were reports about documents that were opened by Qt5-based versions of FeatherNotes but not by its recent versions. All these issues are fixed now.
In addition,
● Theme icons are allowed as node icons by using their names.
● Replacing after searching is made easier (without needing to clear the selection first).
● An asymmetry is corrected between the forward and backward searches/replacements if some text was selected.
● Showing of ampersand in the recent files menu is fixed.
● The minimum required version of Qt is bumped to 6.5.
Use reportFatalUsageError in llvm-omp-kernel-replay (#178371)
All error cases in this tool are usage errors (bad user input, missing
files, malformed JSON) rather than internal LLVM bugs, so
`reportFatalUsageError` is the appropriate replacement.
