devel/py-dasbus: DBus library in Python [New]
Dasbus is a DBus library written in Python 3, based on GLib and inspired
by pydbus. It is designed to be easy to use and extend.
PR: 295125
[Support][Cache] Make `pruneCache` return an `Expected` (#191367)
When `sys::fs::disk_space` would fail in during a call to `pruneCache`,
it would report a `fatal_error`. However, a failure to prune doesn't
mean the caller should fail catastrophically.
Downstream, we use LLVM's cache in the OpenCL runtime. A failure to
prune the cache can be safely ignored without stopping the user's
application.
[AArch64] Don't use GISel for optnone functions if not feasible. (#196343)
A function like the one below should still result in an SME prologue to
set up ZA.
```
void bar() __arm_inout("za");
__attribute__((optnone)) __arm_new("za")
void foo() {
bar();
}
```
https://godbolt.org/z/aEcoKea4b
This worked in LLVM 22, but got broken by #174746.
[AMDGPU][InstCombine] Optimize constant shuffle patterns (#192246)
Detect llvm.amdgcn.wave.shuffle intrinsics where the lane index is a
constant function of the lane ID and replace them with hardware-specific
intrinsics.
[LangRef] Clarify pointer capture spec (#194647)
This clarifies the semantics of "pointer capture" in two respects:
* For provenance capture, specify this in terms of accesses based on the
pointer being UB after the function returns, rather than whether or not
the pointer gets stored etc. The distinction does not matter for
inference, but is commonly required for frontend-generated captures
annotations (and the `!captures` metadata doesn't really make sense
otherwise). This gives provenance (non-)capture unambiguous operational
semantics.
* For address capture, specify that the observable behavior of the
function can't differ based on the address. This is to accommodate
things like loop vectorization runtime checks, which introduce pointer
comparisons on `captures(none)` pointers in a way that is harmless and
needs to be allowed. The semantics here are non-operational. If anyone
has ideas on how to formalize this, they would be very welcome.
[AA] Consider read-only provenance capture for synchronization effects (#197157)
If only read-only provenance is captured, this means that another thread
may only read the object, not write to it. As such, we can also model
synchronizing operations as only reading the location (and thus allow
reordering of reads, but not writes, across the synchronization).
[X86] Manage atomic store of fp -> int promotion in DAG
When lowering atomic <1 x T> vector types with floats, selection can fail since
this pattern is unsupported. To support this, floats can be casted to
an integer type of the same size.
qtcreator: updated to 19.0.1
Qt Creator version 19.0.1 contains bug fixes.
General
Fixed
* That preferences for newly enabled plugins were only available after restart
* Various issues with marking the `Preferences` as dirty
* A possible crash when opening the `About Qt Creator` dialog multiple times
* That using the keyboard shortcut for `Advanced Find` did not raise the search
widget
* Model Context Protocol
* A crash when using the `quit` action
Editing
Fixed
[16 lines not shown]
[SelectionDAG] Scalarize <1 x T> vector types for atomic store
`store atomic <1 x T>` is not valid. This change legalizes
vector types of atomic store via scalarization in SelectionDAG
so that it can, for example, translate from `v1i32` to `i32`.
[X86] Add atomic vector store tests for unaligned >1 sizes.
Unaligned atomic vector stores with size >1 are lowered to calls.
Adding their tests separately here.
