[CycleInfo] Move invalidate() to the result types (#234518)
The new pass manager looks for a custom invalidate() method on the
analysis result type, not on the analysis pass. #188443 added these
methods to CycleAnalysis and MachineCycleAnalysis, so they were never
called and the results were still invalidated by passes that preserve
the CFG. Move them to CycleInfo and MachineCycleInfo.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
find.1: rewrite the -s flag section for clarity
Restructure the description of -s flag:
1. what the option does
2. why it is useful (deterministic order, streaming output)
3. how its results can differ from `find | sort'
Reviewed by: ziaee
MFC after: 3 days
[MC] .fill: fix crash with a zero size (#234535)
`.fill N, 0` creates an MCFillFragment with a value size of 0, which
fails an assertion in writeFragment and divides by zero in release
builds. Since #194164 this affects constant repeat counts as well.
GNU as ignores a zero-size .fill. Do the same.
Fix #227951
[OpenMP][flang] Fix location of reducing worksharing constructs. (#233934)
This fixes issue https://github.com/llvm/llvm-project/issues/222305. The
problem was in 3 places.
1. OpenMPIRBuilder did not set the location on Unreachable and the empty
location later got picked by the builder when the insertion point was
moved onto one of the branches split from it.
2. inlineConvertOmpRegions did not restore the location after calling
convertBlock.
3. initReductionVars did not restore the construct location after the
detour to alloca block.
Co-authored-by: Cursor <cursoragent at cursor.com>
misc/mbuffer: Update to 20261015
Changes according to the ChangeLog in the distribution tar ball:
20261015:
- rollback 20260929
- removed obsolete interlock code needed for Linux < 3.14
- fix for MacOS statistics initialization
20260929 (WITHDRAWN - MacOS already worked since 20251025):
- added MacOS support (patch provided by Robert Smith, WANSecurity, Inc)
20260926:
- prefer info from fpathconf over PIPE_BUF
- integrated some patches from Peter Pentchev
- build fixes
- buffer allocation limitation
- typos and grammar fixes
[mlir][tosa] Clarify signless integer type semantics (#234173)
Update the comment. Explain that signless integers match the TOSA
specification and use signed interpretation unless an operation
specifies otherwise. Clarify that unsigned types and additional bit
widths are dialect extensions, and point to strict validation for
standard conformance.
[libc] Remove full header dependencies from proxy header targets (#234150)
In full-build mode, the proxy headers in libc/hdr/types/ only include
the granular type headers (include/llvm-libc-types/*.h), not the top-
level public headers (which are only included in overlay mode). Having
FULL_BUILD_DEPENDS point at libc.include.<header> was unnecessary and
forced full header generation before building internal targets that only
needed a single type.
Similarly, the function proxy headers in libc/hdr/func/ only include
include/__llvm-libc-common.h in full-build mode, so I've replaced their
dependency on libc.include.stdlib with libc.include.llvm_libc_common_h.
Removing these uncovered a few missing or broken dependencies that were
previously satisfied transitively:
- atexithandler_t depended on the non-existent target
libc.include.llvm-libc-types.atexithandler_t instead of
libc.include.llvm-libc-types.__atexithandler_t (masked by
libc.include.stdlib)
[8 lines not shown]
remove outdated and vulnerable mail/sympa
HOMEPAGE is dead, last update to 6.2.16 and maitainer drop in 2016;
there are four security issues from 2018-2021 effecting our version:
https://www.sympa.community/security/
- Attacker can achieve XSS and so on in message archives.
- Attacker can execute any SOAP call by privileges of any Sympa accounts.
- Attacker can execute arbitrary code with root privileges.
- Possibility to create or modify files on the server filesystem.
OK ian
[Clang][OpenMP] Adds flatten float tripcounts with avoiding `Sema` range checks for float under an int cast (#233521)
Re-lands #229458 and adds the Sema fix that caused its revert (#233657).
`flatten` with a float bound builds an int trip count. That path hit an
assert in `GetValueRange` when a later check looked through an implicit
float->int cast.
One PR, because:
- the Sema-only follow-up needs the float->int flatten change for its
test to pass after the revert.
- #229458 alone would hit the same assert again.
Changes in-short:
- re-landing change
- `GetValueRange` skips non-integer values
[LSR] Keep a single loop exit preference hook
Computing the post-inc exit value already requires the SCEV queries.
The extra target hook does not improve compile time.
Assisted-by: TRAE CLI (GPT-5.6-Sol)
remove outdated and vulnerable mail/sympa
HOMEPAGE is dead, last update to 6.2.16 and maitainer drop in 2016;
there are four security issues from 2018-2021 effecting our version:
https://www.sympa.community/security/
- Attacker can achieve XSS and so on in message archives.
- Attacker can execute any SOAP call by privileges of any Sympa accounts.
- Attacker can execute arbitrary code with root privileges.
- Possibility to create or modify files on the server filesystem.
OK ian
py-wcwidth: updated to 0.9.3
0.9.3
* **Bugfix** libwcwidth no longer has undefined behavior on NULL or empty input in the UTF-8 and
alignment functions
* **Changed** `HyperlinkParams.parse()`_ now rejects trailing text
* **Bugfix** `wrap()`_ should keep a link's own OSC 8 params across a line break
[CodeGenPrepare] Drop poison-generating flags on extensions in optimizeExtUses (#234134)
`optimizeExtUses` rewrites uses of an extension's source in other blocks
to read `trunc` of the extension, which is only correct where the
extension isn't `poison`. A `zext nneg` can be valid only where it was
originally used, like behind a check that its source isn't negative. If
that check is one of the rewritten uses, it ends up reading `poison`,
and on `x86_64-pc-windows-msvc`, InstSimplify in WinEHPrepare's cleanup
folds it to true and causes a miscompile.
Drop the extension's poison-generating flags once a use has been
rewritten, like #72103 and #90382 did for similar cases in
`CodeGenPrepare`.
Fixes #234098.
sysutils/gravityfile: update to 0.4.0
0.4.0 - 2026-10-13
A rewrite of the scanner, the explorer's internals and the command line, with release binaries for macOS, Linux and Windows. It is the first release on crates.io since 0.2.4: 0.3.0 was released on GitHub only, and 0.3.1 was never released, so its changes are listed here. Upgrading from 0.2.4, see also the 0.3.0 notes. Several changes are breaking: the gravityfile executable is gone (use grav), report options and JSON changed (schema_version 2), plugins are Lua only, and settings moved on macOS.
Security
Plugins cannot read past their read-size limit, even when they ask for a larger one, and cannot read special files such as FIFOs, which could block.
An archive cannot be created inside the directory being archived, and an interrupted archive leaves nothing behind.
zip is updated to 9.0, past RUSTSEC-2026-0367, -0368 and -0369. Those affect zip's own extraction helpers, which grav never used: its extraction already drops setuid and setgid bits and keeps symlinks inside the destination. Opening a ZIP still reads only its directory, not the whole archive, which zip 9 would otherwise scan.
Dependencies are updated past the vulnerable crossbeam-epoch 0.9.18 and the unsound git2 0.20 line; BLAKE3's unused memory-mapping feature, and with it memmap2, is gone.
Added
grav diff OLD [NEW] shows what grew, shrank, appeared or went between two scans, largest changes first per directory. Each side is a snapshot or a directory; with one snapshot it is compared with the same place today, scanned with the snapshot's scope. Text or JSON.
Plugins that work as documented. Hooks run in the background, so a slow plugin no longer freezes navigation; only on_delete_start (which can refuse the delete) and on_shutdown are awaited. gf.notify now shows its message in the status line, plugin failures are reported instead of only logged, and hooks receive the context (directory, theme, selected entry) as a third argument. Scan start and error, delete, copy, move and rename completion, and analysis hooks now fire. Hooks the explorer never fired and the unrendered ui namespace are removed, and the plugin guide and example are rewritten to match.
grav scan --top N lists the largest files anywhere below the root, and grav scan --by-type totals the space by file extension.
Scan history. Each full scan in the explorer, and grav scan --record, adds a summary to history.jsonl in the data directory. grav history [PATH] shows a directory's size over time and what changed most; --all lists every recorded directory. The explorer's header shows the change since the last scan of the same place. record_history = false turns it off.
Browse snapshots in the explorer. grav root.json.zst opens a saved scan or ncdu dump read-only, without touching the filesystem: navigation, search, the treemap, size toggling and age analysis work; file operations, rescans and duplicate detection are refused with an explanation.
[75 lines not shown]
