NAS-139068 / 26.04 / Prevent HA propagation on directoryservices.setup (#17897)
The fix for NAS-139002 already makes the ha_propagate here a no-op. This
commit ensures we are consistently applying service options when
restarting dependent services.
mimetreeparser: add version 25.08.3
This repository contains a parser for a MIME tree and is based on KMime. The
goal is given a MIME tree to extract a list of parts (e.g. text, html) and a
list of attachments, check the validity of the signatures and decrypt any
encrypted part.
blocklist: blacklist: Chase recent upstream changes
Upstream fixed a couple of bugs:
1. Only attempt to restore the blocking rules if the database file
exists. Otherwise, when the service starts for the first time, it
fails (PR 258411).
2. Revert a commit that removed a call to close(bi->bi_fd), preventing
the descriptor from being deleted.
PR: 258411
PR: 291680
MFC after: 1 week
(cherry picked from commit 9c844b6110b3768a4fc3ce47cd9d1b30915213ec)
blocklist: Add vendor import instructions
Add vendor import instructions for blocklist.
It includes a "freebsd-changes.sh" script that takes care of adapting
paths and functions into FreeBSD.
Reviewed by: emaste
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D49510
(cherry picked from commit 715cc257137099e022c7eecea4cd6995bb7604a3)
[clang][CodeGen] Promote point of GRO(CWG2563) (#151067)
This patch implement piece of the proposed solution to
[CWG2563](https://cplusplus.github.io/CWG/issues/2563.html):
> [9.6.4 dcl.fct.def.coroutine.p8] This return exits the scope of gro.
It exits the scope of promise only if the coroutine completed without
suspending.
If a coroutine completes without suspending, it does not exit the scope
of the promise until GRO conversion is done, because GRO conversion is
considered part of the coroutine execution. The current behavior
performs conversion after coroutine state cleanup, which does not
conform to the standard:
``` LLVM
before.cleanup:
; ...
br label %coro.cleanup
[43 lines not shown]
[SLP] Skip MMRA metadata if instruction can't have it (#173319)
Exposed by recent commit in e644f06c2ffc, but the wrong propagation
might be applied in other situations too.
Without this, we will get verification errors with e644f06c2ffc.
!mmra metadata attached to unexpected instruction kind
%3 = fmul <2 x float> %2, <float 1.000000e+00, float 0.000000e+00>,
!mmra !1
[llvm][CMake] Remove -fno-lifetime-dse (#173322)
Now that #24952 has been fixed by #170575, we no longer need to specify
-fno-lifetime-dse when building with gcc.
