net/telemt: unbreak i386 build introduced by upstream changes
Create extra patch for i386 architecture, using 4Gb
constant that fits into i386 usize variable.
PR: 298112
Reported by: Vladimir Grebenshchikov <vova at zote.me> (maintainer)
Approved by: osa, vvd (Mentors, implicit)
[CIR][NFC] Share getSuccessorRegions across region-branch ops
Six of the ten CIR ops implementing RegionBranchOpInterface reported the same
successors: any of their regions may be entered from the parent operation, and
every region exit goes back to it. Add a CIR_EnterAnyRegionBranchOpBase class
that appends that definition to the one inherited from CIR_RegionBranchOpBase,
retarget the six ops onto it and delete their hand-written definitions.
The shared definition walks getRegions() rather than naming region accessors.
For all six ops the entry regions were exactly the declared regions in
declaration order, so it reports the same successors in the same order. The doc
comments of the deleted ScopeOp and TernaryOp definitions go with them, instead
of being left behind on the neighbouring builders.
IfOp, GlobalOp, TryOp and AwaitOp stay on the base class, since their successors
depend on the operation: IfOp falls back to the parent when the else region is
empty, GlobalOp skips its optional ctor and dtor regions, TryOp iterates
variadic handler regions, and AwaitOp routes ready to resume and suspend.
krb5.conf: alias realm case variants and fix domain_realm
MIT krb5 matches [realms] sections case-sensitively, and we set
dns_lookup_kdc = false whenever KDCs are pinned. Samba reconnects as
the machine account after creating it, kiniting as
MACHINE$@<dns_domain_name>, and that name comes from
lsa_QueryInfoPolicy2 in lower case. The lookup misses our upper-case
realm section, has no DNS fallback, and fails with KRB5_REALM_UNKNOWN.
SPNEGO normally falls back to NTLMSSP and the join survives. With the
GPOS STIG enabled smb.conf carries client use kerberos = required,
leaving no other mechanism, so every fresh AD join fails with
WERR_GEN_FAILURE.
Emit each realm under both case spellings sharing the same pinned
KDCs, and take default_domain from the canonical name.
Also rename [domain_realms] to [domain_realm]. MIT krb5 only reads the
singular form, so the section was parsing cleanly and being ignored.
[2 lines not shown]
krb5.conf: alias realm case variants and fix domain_realm
MIT krb5 matches [realms] sections case-sensitively, and we set
dns_lookup_kdc = false whenever KDCs are pinned. Samba reconnects as
the machine account after creating it, kiniting as
MACHINE$@<dns_domain_name>, and that name comes from
lsa_QueryInfoPolicy2 in lower case. The lookup misses our upper-case
realm section, has no DNS fallback, and fails with KRB5_REALM_UNKNOWN.
SPNEGO normally falls back to NTLMSSP and the join survives. With the
GPOS STIG enabled smb.conf carries client use kerberos = required,
leaving no other mechanism, so every fresh AD join fails with
WERR_GEN_FAILURE.
Emit each realm under both case spellings sharing the same pinned
KDCs, and take default_domain from the canonical name.
Also rename [domain_realms] to [domain_realm]. MIT krb5 only reads the
singular form, so the section was parsing cleanly and being ignored.
[2 lines not shown]
NAS-142772 / 27.0.0-BETA.1 / krb5.conf: alias realm case variants and fix domain_realm (#19562)
MIT krb5 matches [realms] sections case-sensitively, and we set
dns_lookup_kdc = false whenever KDCs are pinned. Samba reconnects as the
machine account after creating it, kiniting as
MACHINE$@<dns_domain_name>, and that name comes from
lsa_QueryInfoPolicy2 in lower case. The lookup misses our upper-case
realm section, has no DNS fallback, and fails with KRB5_REALM_UNKNOWN.
SPNEGO normally falls back to NTLMSSP and the join survives. With the
GPOS STIG enabled smb.conf carries client use kerberos = required,
leaving no other mechanism, so every fresh AD join fails with
WERR_GEN_FAILURE.
Emit each realm under both case spellings sharing the same pinned KDCs,
and take default_domain from the canonical name.
Also rename [domain_realms] to [domain_realm]. MIT krb5 only reads the
singular form, so the section was parsing cleanly and being ignored.
[MLIR][ODS] Add enum operation format directive (#220412)
Today enum handling is problematic: their format is defined manually
often with `<$value>` so that their generic printing is
`#dialect.mnemnonic<value>` instead of `#dialect<mnemnonic value>`.
However that prevents the Operation ODS assembly format from getting
just the value without the surrounding `<` `>`.
Add enum($attr) to declarative operation assembly formats. The directive
parses and prints the symbolic enum value independently of the
attribute's custom assembly format. This lets standalone attributes
retain delimiters while operations use a bare value.
Validate directive operands during TableGen processing and retain
keyword and quoted-string handling. Add separator-aware parsing and
unquoted printing for comma- and vertical-bar-separated bit enums.
Document the directive and add generated-code, diagnostic,
compatibility, and runtime round-trip coverage.
Assisted-by: Codex
[GlobalsAA] Fix handling of optnone functions (#220546)
For optnone functions, we want to fall back to the memory effects
implied by attributes. However, the code that did this repeatedly
checked only the first function in the SCC, instead of all functions.
Disclaimer: Test case is AI generated, rest is my own.
[llvm] Initialize function_ref callable state (#220561)
An empty function_ref leaves its callable member uninitialized. Implicit
copy operations propagate that value and operator== reads it when empty
references are compared.
Without the initialization, Valgrind reports the new regression test as:
Conditional jump or move depends on uninitialised value(s)
ERROR SUMMARY: 79 errors from 7 contexts
Initialize callable to zero and cover empty construction, copying,
assignment, and equality. The same Valgrind run then reports zero
errors.
Assisted-by: Codex
[CIR][NFC] Share getSuccessorRegions across region-branch ops
Six of the ten CIR ops implementing RegionBranchOpInterface reported the same
successors: any of their regions may be entered from the parent operation, and
every region exit goes back to it. Add a CIR_EnterAllRegionsOpBase class that
appends that definition to the one inherited from CIR_RegionBranchOpBase,
retarget the six ops onto it and delete their hand-written definitions.
The shared definition walks getRegions() rather than naming region accessors.
For all six ops the entry regions were exactly the declared regions in
declaration order, so it reports the same successors in the same order. The doc
comments of the deleted ScopeOp and TernaryOp definitions go with them, instead
of being left behind on the neighbouring builders.
IfOp, GlobalOp, TryOp and AwaitOp stay on the base class, since their successors
depend on the operation: IfOp falls back to the parent when the else region is
empty, GlobalOp skips its optional ctor and dtor regions, TryOp iterates
variadic handler regions, and AwaitOp routes ready to resume and suspend.
[AMDGPU] si-peephole-sdwa: Simplify selection combine tests (NFC) (#219933)
The second SDWA instruction in each test case is not involved in the
SDWA conversion being tested.
Remove the unnecessary and confusing instructions.
