[libc] Define TCP_CM_INQ (#239982)
The kernel's headers name the control message type that TCP_INQ asks for
separately. gRPC reads the byte count back by that name and does not
define it when TCP_INQ is already defined, so it did not compile.
Assisted-by: Claude
[clang] Fix ARM64X driver checks for in-process cc1 (#240278)
I missed updating `arm64x.c` in #222531. It uses `CHECK-NEXT` between
the two cc1 commands, but in-process execution now prints `(in-process)`
between them, causing the Fuchsia buildbot failure.
This adjusts the check and adds explicit coverage for both cc1 modes.
Both pass locally. Could we take this small test-only follow-up without
reverting and relanding #222531?
System: Configuration: Backups - add dropdown field type for backup providers (#11170)
A provider field of type dropdown renders as a selectpicker from its options (value => label), with the stored value selected, so a setting with a fixed set of values no longer has to be a text box checked after saving.
(cherry picked from commit 4f968addd5ec23d7099b674e2e9ad441080d29a0)
[Analysis] Use method LLVM_ABI annotations for Loop (#231792)
The `Loop` class has no virtual methods, and thus no vtable that needs
to be exported, so class-level annotations are not necessary for this
class.
The effort to build LLVM as a dylib is tracked in #109483.
[X86] Match PMULHRSW from rounding shift patterns (#232679)
Fixes #196666. As far as I can tell X86 only ever produces PMULHRSW when
you call the intrinsic, so the usual fixed point multiply you see in
video codecs and audio filters ends up as a long pmaddwd/shift/shuffle
sequence instead of the one instruction. This patch teaches
combineTruncate to spot trunc((X*Y + (1 << (N-1))) >> N) for N up to 15,
and when it can show that Y still fits in 16 bits after scaling it by 1
<< (15-N) it emits PMULHRSW instead. I ran every N, X and in range Y
against the real instruction to make sure it's exact, and pr119158.ll
kinda accidentally picks it up as an N=7 case
[lldb] Remove _ENABLE_EXTENDED_ALIGNED_STORAGE (#239286)
This was added in February 2019 in 9d0c5f9953e8 to work around issues
with VS 2017's `make_shared` implementation, and `aligned_union`. This
no longer holds true today as there are no remaining uses of
`aligned_union` and `aligned_storage`; and MSVC's `make_shared`
implementation no longer depends on either of these, as they have been
deprecated in C++23.
This removes warnings when building with PCHs.
devel/gerrit: update to 3.14.5, fix pkg-message
The top-level pkg-message shadowed files/pkg-message.in, so users saw
literal %%DATADIR%% placeholders. Remove it and add the template to
SUB_FILES. Also substitute PORTVERSION in the documentation link.
Release notes: https://www.gerritcodereview.com/3.14.html
libssl: stop inspecting cert signatures for seclevel
As pointed out by dadrian to OpenSSL in #31195, it makes no sense
to inspect our certificate's signatures. Our stack may not even
know the algorithms our CA used (think some PQ CA, for example).
What matters to us is that we don't use a key that is too weak,
so keep the check for that.
We do not currently inspect the peer's cert for strength either.
That may be an omission/bug.
On side effect of this removal is that we do no longer ensure that
a RSA-PSS cert has a salt length matching the hash length. That's
not really part of security, and if we care to restore this for
reasons of compliance, we should think about where to put it in
a way that throws a better error than 'ca md too weak'
Prompted by a report by semarie.
[2 lines not shown]
libssl: stop inspecting our cert chain for "security"
The chain signing our leaf cert is not crypto we ourselves use. The peer
can decide that the weak crypto is unacceptable if they care.
ok beck
System: Access - add authority/unrestricted to legacy pages to explain all of these should be handled with additional care (#11160)
(cherry picked from commit 3d68473e0bb1b720f1b87a666c70764fdd21c524)
