net/gnome-online-accounts: update to 3.54.10
Update to 3.54.10.
Overview of changes in 3.54.10
==============================
* Bugs fixed:
- #442 Unclear which part of "IMAP+SMTP" account test failed
- #450 adding nextcloud account which has a subfolder does not work
- !374 goadaemon: Handle broken account configs
net/gnome-online-accounts: update to 3.54.9
Update to 3.54.9
Overview of changes in 3.54.6
=============================
* Translation updates:
- Dutch (Nathan Follens)
- Slovak (Dušan Kazik)
- Thai (Aefgh Threenine)
- Uighur (Abduqadir Abliz)
Overview of changes in 3.54.7
=============================
* Bugs fixed:
- #417 Support for saving a Kerberos password after the first login
- #436 Changing expired kerberos password is not supported
- #437 Provided Files URI does not override undiscovered endpoint
- #439 DAV client rejects 204 status in OPTIONS request handler
[13 lines not shown]
[RISCV] Fix ordering of CHECK prefixes in some tests to mitigate UTC bug. NFCI (#181259)
This patch fixes the exact same problem as #173125 . Where certain order
of CHECK prefixes will somehow causing UTC to incorrectly (re)generate
surplus check lines and failed the tests.
[mlir][tensor]-Handle Dynamic Offset in BubbleUpSliceOpThroughCollapse (#178921)
This patch extends the `BubbleUpExtractSliceThroughCollapseShape`
pattern to handle cases where `tensor.extract_slice` has a dynamic
offset.
During tile and fuse transformations, it is common to encounter IR where
`tensor.extract_slice` operations appear after `tensor.collapse_shape`.
These patterns are used as cleanup transformations to canonicalize the
IR by bubbling up the slice operation before the reshape. This enables
further optimizations and simplifications downstream.
Previously, the pattern only handled:
1. Static offsets and sizes.
2. Dynamic sizes with a single non-unit expanded dimension.
This left a gap for additional common cases where we may have:
- Dynamic offsets with size == 1 (single element extraction).
- Size greater than 1 but the offset is computed dynamically.
[23 lines not shown]
[VPlan] Check scalar VF in removeRedundantCanonicalIVs.
When the plan has only a scalar VF, we never generate vectors for IVs,
so we can always perform the replacement.
[AMDGPU] Disable generic DAG combines at -O0 to preserve debuggability.
Disable generic DAG combines for AMDGPU at -O0 via disableGenericCombines()
to preserve instructions that users may want to set breakpoints
on during debugging.
Since power-of-2 division/remainder for types > i64 was dependent on
DAG combine optimizations, added shouldExpandPowerOf2DivRem()
to request IR-level expansion for these cases at -O0.
workflows/release-documentation: Add release environment (#181063)
This way we can limit access to the secrets to the main and release
branches.
This is a partial re-commit of b6ee085068972a41f3b2735a9f7e3ca48eab0f00
[CIR] Add CIRGen support for static local variables with non-constant initializers
This adds CIRGen infrastructure for C++ function-local static variables
that require guarded initialization (Itanium C++ ABI).
Changes:
- Add ASTVarDeclAttr to carry VarDecl AST through the pipeline
- Add emitGuardedInit() to CIRGenCXXABI for guarded initialization
- Add emitCXXGuardedInit() to CIRGenFunction
- Replace NYI in addInitializerToStaticVarDecl() with ctor region emission
- Set static_local attribute on GlobalOp and GetGlobalOp
The global's ctor region contains the initialization code, which will be
lowered by LoweringPrepare to emit the actual guard variable pattern with
__cxa_guard_acquire/__cxa_guard_release calls.
[clang] Mark `PrivateFieldNames.def` as textual header in module map (#181250)
When building with modules enabled (`LLVM_ENABLE_MODULES=ON`), the
module system attempts to transform the inclusion of
`PrivateFieldNames.def` into a module import. Since this `#include`
appears inside the `SerializationFormat` class definition (to generate
accessor methods via macros), the resulting module import violates C++
modules rules that imports must appear at file scope. The fix is to mark
`PrivateFieldNames.def` as a textual header in the `Clang_Analysis`
module to ensure the file is processed as a traditional textual include.
rdar://170257449
