[MLIR][Python] Add C and Python API for `mlir::DynamicAttr` (#182820)
This PR adds C and Python API support for `mlir::DynamicAttr`. It
primarily enables attributes in dialects that are dynamically generated
via IRDL to be constructed in Python, and allows retrieving the
parameters contained in a dynamic attribute from Python.
This PR is quite similiar to #182751, so I use tab to autocomplete some
code via github copilot, but manually verified.
[Flang][OpenMP] Fix crash privatizing USE'd module variable in BLOCK (#182060)
Module variables accessed via USE inside a BLOCK nested in an OpenMP
construct (parallel do, taskloop) crash during lowering because the host
symbol box doesn't exist yet — the BLOCK hasn't been lowered when
privatization runs.
The fix instantiates the module global on demand in the
DataSharingProcessor before privatization, and adds a fallback from
lookupOneLevelUpSymbol to lookupSymbol in privatizeSymbol for symbols
bound at the current scope level.
Fixes : [#161183 ](https://github.com/llvm/llvm-project/issues/161183)
---------
Co-authored-by: Chandra Ghale <ghale at pe31.hpc.amslabs.hpecorp.net>
[lldb] address memory leakage in lldb-server (#177572)
lldb-server has exhibited fairly unexpected behaviour. The time each
iteration of the main loop takes (attach + spawn a child process) has
been progressively increasing over the course of the lldb-server
execution. For instance, at the beginning of the remote tests run (when
a single instance of lldb-server on the remote side processes all the
incoming connections), each iteration took approximately 0.1 seconds,
increasing to 1.5 seconds by the end.
The analysis of the lldb-server application indicates that the
__libc_fork function takes more and more time on each iteration. The
most plausible interpretation of this fact would appear to be that the
application accumulates a certain resource that the fork function
subsequently had to process.
The following investigation has shown that the memory leakage did seem
to take place during the lldb-server execution. After the spawn of a
child process lldb-server additionally creates a monitoring thread, the
[25 lines not shown]
[CodeCompletion] Consider header files without extension, if... (#166447)
... the path passed to -I ends with /include.
I've brought it up, when the special handling for Qt was added
(https://reviews.llvm.org/D112996#3349609) but got no feedback.
fix gffb_putchar_mono():
- don't use the glyph cache - it doesn't buy us anything when drawing mono
characters and it can't deal with WSATTR_HILIT
- gffb_sync() before drawing characters - turns out we can overrun the command
buffer with this, which leads to occasional lockups. No measurable loss of
speed.
[InstCombine] Only ignore first zero index during GEP canonicalization (#180764)
When canonicalizing GEPs to have a single index, only ignore the first
leading zero index. This fixes a hole in the canonicalization in case
there was a struct zero offset, which can't be removed by the the
leading zero stripping.
[mlir][Linalg] Allow isaBroadcastOpInterface to accept LinalgOp (#182806)
Allow isaBroadcastOpInterface to accept LinalgOp so that both the named
linalg.broadcast op and broadcast-like linalg.generic are handled by a
single API instead of special-casing check for named vs generic op in
downstream projects.
No test is being added for this change because callers that pass
GenericOp (e.g. Specialize.cpp) continue to work since GenericOp is a
LinalgOp.
Signed-off-by: Abhishek Varma <abhvarma at amd.com>
[AArch64] -aarch64-enable-global-isel-at-O=-1 should disable GISel (#182250)
Recent changes in #174746 to use GISel for optnone functions broke this.
Now at O3 -aarch64-enable-global-isel-at-O=-1 is having the opposite
affect of actually enabling GISel instead of SDAG and at O0 FastISel is
no longer used. I've added a check for if this is disabled.
py-typeguard: updated to 4.5.1
**4.5.1** (2026-02-19)
- Fixed iterable unpacking incorrectly calculating the cut-off offset of the item list
when assigning remaining values to the star variable
adguardhome: updated to 0.107.72
0.107.72
Security
Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.25.7.
Added
AdGuard Home now tracks the TLS certificate and key files for updates and reloads them after any updates are detected.
New query parameter recent in GET /control/stats/ defines statistics lookback period in millieseconds. See openapi/openapi.yaml for details.
New field "ignored_enabled" in GetStatsConfigResponse or GetQueryLogConfigResponse. See openapi/openapi.yaml for details.
Changed
In addition to modifying the contents of a hosts file, deleting or renaming the file now also updates runtime clients and DNS filtering results.
[6 lines not shown]
[Clang][CodeGen] Fix __builtin_counted_by_ref for nested struct FAMs (#182575) (#182590)
GetCountedByFieldExprGEP() used getOuterLexicalRecordContext() to find
the RecordDecl containing the counted_by count field. This walks up
through all lexically enclosing records to find the outermost one, which
is wrong when a struct with a counted_by FAM is defined nested inside
another named struct.
For example, when struct inner (containing the FAM) is defined inside
struct outer, getOuterLexicalRecordContext() resolves to struct outer
instead of struct inner. The StructAccessBase visitor then fails to
match the base expression type (struct inner *) against the expected
record (struct outer), returning nullptr. This nullptr propagates back
as the GEP result, and the subsequent dereference in
*__builtin_counted_by_ref() triggers an assertion failure in
Address::getBasePointer().
Replace getOuterLexicalRecordContext() with a walk that only traverses
anonymous structs and unions, which are transparent in C and must be
[15 lines not shown]
shells/oh-my-posh: update to 29.6.1
v29.6.1
Bug Fixes
pwsh: never output BOM for init scripts (4a2d995)
v29.6.0
Bug Fixes
pwsh: set status before executing stream (0cb58c3), closes #7331
Features
os: add zorin os icon (fefd73a)
devel/cargo-nextest: update to 0.1.129
Changed
--show-progress=only now behaves like the default auto in non-interactive mode, showing successful tests with a counter. This change was made because only is primarily intended for interactive scenarios. (#3087)
The MSRV for building nextest has been updated to Rust 1.91.
Fixed
Setup scripts that write NEXTEST-prefixed environment variables to $NEXTEST_ENV now properly report failure. Previously, the setup script would be reported as successful despite invalid variables, and tests would still run. (#3094)
Internal improvements
Replay output is now only loaded from the archive when needed. This makes replays around 10-15% faster. (#3090)
Switched from the zip crate to eazip to address repeated semver breakage in the zip crate. (#3093)
[AArch64] Add bfloat patterns for `partial_reduce_fmla` (#181982)
A BFMLALT/B pair exactly matches the semantics of a partial_reduce_fmla
from (nx)v8bf16 to (nx)v4f32.
