[clang] Use tighter lifetime bounds for C temporary arguments
In C, consecutive statements in the same scope are under
CompoundStmt/CallExpr, while in C++ they typically fall under
CompoundStmt/ExprWithCleanup. This leads to different behavior with
respect to where pushFullExprCleanUp inserts the lifetime end markers
(e.g., at the end of scope).
For these cases, we can track and insert the lifetime end markers right
after the call completes. Allowing the stack space to be reused
immediately. This partially addresses #109204 and #43598 for improving
stack usage.
Use setExprNeedsCleanups in BuildCXXNew and avoid breaking c++98
This approach is much cleaner, but broke checkICE reporting in c++98.
Stepping through a debugger shows that this happend because the
static_assert test didn not recognize ExprWithCleanups as transparent to
constant evaluation. To addresse this, we update CheckICE to recurse
into the sub-expression, and keep the old behavior.
[clang] Use uniform lifetime bounds under exceptions
To do this we have to slightly modify how some expressions are handled
in Sema. Principally, we need to ensure that calls to new for
non-trivial types still have their destructors run. Generally this isn't
an issue, since these just get sunk into the surrounding scope. With
more lifetime annotations being produced for the expressions, we found
that some calls to `new` in an unreachable switch arm would not be
wrapped in ExprWithCleanups. As a result, they remain on the EhStack
when processing the default label, and since the dead arm doesn't
dominate the default label, we can end up with a case where the def-use
chain is broken (e.g. the def doesn't dominate all uses). Technically
this path would be impossible to reach due to the active bit, but it
still failed to satisfy a dominance relationship.
With that in place, we can remove the constraint on only using tighter
lifetimes when exceptions are disabled.
[clang] Use tighter lifetime bounds for C temporary arguments
In C, consecutive statements in the same scope are under
CompoundStmt/CallExpr, while in C++ they typically fall under
CompoundStmt/ExprWithCleanup. This leads to different behavior with
respect to where pushFullExprCleanUp inserts the lifetime end markers
(e.g., at the end of scope).
For these cases, we can track and insert the lifetime end markers right
after the call completes. Allowing the stack space to be reused
immediately. This partially addresses #109204 and #43598 for improving
stack usage.
Use setExprNeedsCleanups in BuildCXXNew and avoid breaking c++98
This approach is much cleaner, but broke checkICE reporting in c++98.
Stepping through a debugger shows that this happend because the
static_assert test didn not recognize ExprWithCleanups as transparent to
constant evaluation. To addresse this, we update CheckICE to recurse
into the sub-expression, and keep the old behavior.
[clang] Use uniform lifetime bounds under exceptions
To do this we have to slightly modify how some expressions are handled
in Sema. Principally, we need to ensure that calls to new for
non-trivial types still have their destructors run. Generally this isn't
an issue, since these just get sunk into the surrounding scope. With
more lifetime annotations being produced for the expressions, we found
that some calls to `new` in an unreachable switch arm would not be
wrapped in ExprWithCleanups. As a result, they remain on the EhStack
when processing the default label, and since the dead arm doesn't
dominate the default label, we can end up with a case where the def-use
chain is broken (e.g. the def doesn't dominate all uses). Technically
this path would be impossible to reach due to the active bit, but it
still failed to satisfy a dominance relationship.
With that in place, we can remove the constraint on only using tighter
lifetimes when exceptions are disabled.
NFS: prevent boot-time service failures before system dataset is available
nfs-server and its dependencies (nfs-mountd, nfsdcld, rpc-statd) fail
at boot when the system dataset (/var/db/system/nfs) is not yet mounted.
The system dataset lives on the data pool which is imported by middleware
after boot, but systemd auto-starts nfs-server (it's enabled) before
middleware runs.
Keep nfs-server disabled in systemd so it never auto-starts at boot.
Since nfs-server doesn't start, its dependency chain (nfs-mountd,
nfsdcld, rpc-statd, nfs-idmapd) is not pulled in either — eliminating
all boot-time NFS failures.
Middleware already manages NFS lifecycle explicitly:
- HA: failover event handler calls restart_services() after pool import
- Non-HA: pool_post_import hook now starts NFS if enabled but not running
systemctl start/restart works on disabled services, so all existing
middleware service management (service.start, service.restart,
[6 lines not shown]
tex-l3kernel{,-doc}: update to 2026
## [2026-03-20]
### Added
- `en`-type variants of `\text_...case:nn`
### Changed
- Adjust internal expansion in case functions to support `biblatex`
(transitional measure)
## [2026-03-16]
### Added
- `\box_(g)frame:Nnn` and `\box_(g)underline:Nnn`
- `\vbox:w`, `\vbox_top:w`, `\vbox_center:w` and their `:nw` and
`_to_ht:nw` versions
- Debugging switch `check-assertions`, `\debug_assert:nN(n)`, and
`\debug_assert:nn(n)` (issue \#1840)
[20 lines not shown]
[AMDGPU] Fix i16/i8 flat store in true16 with sramecc (#190238)
The pattern was guarded by the D16PreservesUnusedBits predicate
which is not needed for stores.
