[clang][bytecode] Remove an incorrect assertion (#179644)
There are situations where DiscardResult is set, but we still wish to
emit a float value, e.g. when we will discard the result of an operation
involving such a float value.
multimedia/hyprpwcenter: Add port: GUI Pipewire control center
hyprpwcenter is a GUI control center for pipewire. It allows to look
and configure nodes, outputs, and adjust the pw graph.
WWW: https://github.com/hyprwm/hyprpwcenter
[flang] fix early free of allocatable function result in WHERE mask (#178691)
Fix https://github.com/llvm/llvm-project/issues/168561.
The issue was that the allocatable function result used as WHERE mask
was freed too early.
This happened because lowering was moving the result via as_expr but was
still inserting the deallocation directly on the storage instead of
passing that responsibility to the moved value (hlfir.expr). Later, the
pass optimizing WHERE is extending the expr lifetime usage passed the
deallocation of the storage because it (rightfully) assumes it can
extent lifetime of hlfir.expr as long as it moves the related destroy.
Fix lowering to pass the storage ownership to the expression after the
call instead.
[clang][bytecode] Reject void ArraySubscriptExprs (#179619)
This happens in C when we subscript an expression of type void*, but
there's nothing for us to do here. Just reject it early.
Fixes https://github.com/llvm/llvm-project/issues/177758
[flang][OpenMP] Leave local automatic variables alone (#178739)
There is code in resolve-directives.cpp that tries to apply DSA flags to
symbols encountered inside constructs. This code was written with the
assumption that all such symbols will be declared outside of the
construct.
When a symbol declared in a BLOCK construct nested in a construct was
found, the code would attempt to either privatize or share it in the
enclosing construct (where the symbol didn't exist) leading to trouble.
BLOCK constructs (and thus the possibility of having local variables)
was introduced in F2008.
The first OpenMP spec that considered F2008 was 5.0, where the behavior
of the BLOCK construct was explicitly left unspecified. From OpenMP 5.1
onwards, all local non-static variables are private in the construct
enclosing the declaration. This PR extends this behavior retroactively
to all prior OpenMP versions.
Fixes https://github.com/llvm/llvm-project/issues/178613
[AMDGPU] Add machineFunctionInfo to recent MIR tests (#179602)
Initialize machineFunctionInfo in recently added MIR tests to assist in
downstream testing.
[clang-tidy] Allow type-generic builtins in pro-type-vararg check (#178656)
## Summary
Add type generic builtins to the allowed variadics list in the
`cppcoreguidelines-pro-type-vararg` check (also used by `hicpp-vararg`):
- `__builtin_clzg`
- `__builtin_ctzg`
- `__builtin_popcountg`
- `__builtin_bswapg`
## Root Cause
These builtins are declared as variadic (`int(...)`) to accept any
integer type via `CustomTypeChecking`. However, they are not C style
vararg functions , they take exactly one argument of a generic integer
type.
## Test
Added test cases in `pro-type-vararg.cpp` to verify no warning is
emitted.
Fixes #178629
py-queuelib: updated to 1.9.0
Version 1.9.0
* Added support for Python 3.14
* Removed support for Python 3.9 and PyPy 3.10
* Improved linting and CI configuration
www/py-django-post_office: Update to 3.11
* Switch to the PEP517 build framework.
* Remove no longer required USE_LOCALE as the UTF-8 mode is enabled
by default when the locale is C since Python 3.7.
Changelog since 3.9.1:
https://github.com/ui/django-post_office/blob/v3.11/CHANGELOG.md
PR: 292602
Approved by: maintimer timeout (14+ days)
www/py-django-post_office: Update to 3.11
* Switch to the PEP517 build framework.
* Remove no longer required USE_LOCALE as the UTF-8 mode is enabled
by default when the locale is C since Python 3.7.
Changelog since 3.9.1:
https://github.com/ui/django-post_office/blob/v3.11/CHANGELOG.md
PR: 292602
Approved by: maintimer timeout (14+ days)
py-asgiref: updated to 3.11.1
3.11.1 (2026-02-03)
* SECURITY FIX CVE-2025-14550: There was a potential DoS vector for users of
the ``asgiref.wsgi.WsgiToAsgi`` adapter. Malicious requests, including an unreasonably
large number of values for the same header, could lead to resource exhaustion
when building the WSGI environment.
To mitigate this, the algorithm is changed to be more efficient, and
``WsgiToAsgi`` gains a new optional ``duplicate_header_limit`` parameter,
which defaults to 100. This specifies the number of times a single header may
be repeated before the request is rejected as malformed.
You may override ``duplicate_header_limit`` when configuring your application::
application = WsgiToAsgi(wsgi_app, duplicate_header_limit=200)
Set ``duplicate_header_limit=None`` if you wish to disable this check.
[3 lines not shown]
