[RFC][IR] Remove `Constant::isZeroValue`
`Constant::isZeroValue` currently behaves same as `Constant::isNullValue` for
all types except floating-point, where it additionally returns true for negative
zero (`-0.0`). However, in practice, almost all callers operate on
integer/pointer types where the two are equivalent, and the few FP-relevant
callers have no meaningful dependence on the `-0.0` behavior.
This PR removes `isZeroValue` to eliminate the confusing API surface. All
callers are changed to `isNullValue` with no test failures.
`isZeroValue` will be reintroduced in a future change with clearer semantics:
when null pointers may have non-zero bit patterns, `isZeroValue` will check for
bitwise-all-zeros, while `isNullValue` will check for the semantic null (which
may be non-zero).
Add files missed in 56a7ce8416d181a2060d7a42
Skip usr.bin/diff3 tests as these contain text that gets misinterpreted
as merge conflict markers and blocks push with the relevant pre-receive
hook.
PR: 293186
[ELF,PPC64] Scope checkPPC64TLSRelax to section and simplify TLS markers
checkPPC64TLSRelax detects TLS GD/LD without TLSGD/TLSLD markers
(generated from old IBM XL) and disables TLS optimization. Previously it
set a per-file flag (ppc64DisableTLSRelax). Now scope it in the section
being scanned.
In addition, simplify the R_PPC64_TLSGD/R_PPC64_TLSLD marker handling:
the redundant `sym.setFlags(NEEDS_TLSIE)` is unnecessary as the
preceding GOT_TLSGD relocation already sets it.
[DAGCombiner] Fold trunc(build_vector(ext(x), ext(x)) -> build_vector(x,x) (#179857)
The original implementation performed the transformation when
isTruncateFree was true:
truncate(build_vector(x, x)) -> build_vector(truncate(x), truncate(x)).
In some cases, x comes from an ext, try to pre-truncate build_vectors
source operands
when the source operands of build_vectors comes from an ext.
Testcase from: https://gcc.godbolt.org/z/bbxbYK7dh
asmc: Add MacPro3,1 temperature sensor support
Test and verified with Sonicblue7
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54952
[clang][Python] Use fstrings instead of string concatenations (#173861)
This PR replaces string concatenations and the older `%` string
interpolation with fstrings. These changes were originally part of
#173845 but have been moved to a new PR.
[ELF] Add target-specific relocation scanning for PPC32 (#181517)
Implement PPC::scanSectionImpl, following the pattern established for
x86 (#178846) and PPC64 (#181496). This merges the getRelExpr and TLS
handling for SHF_ALLOC sections into the target-specific scanner,
enabling devirtualization and eliminating abstraction overhead.
- Inline relocation classification into scanSectionImpl with a switch
on relocation type, replacing the generic rs.scan() path.
- Use processR_PC/processR_PLT_PC for common PC-relative and PLT
relocations.
- Handle R_PPC_PLTREL24 inline with addend masking via processAux,
removing the EM_PPC special case from process().
- Handle TLS GD/LD/IE directly, eliminating handleTlsRelocation,
getTlsGdRelaxSkip, and adjustTlsExpr overrides. Use handleTlsIe
for TLS IE, and handleTlsGd for R_PPC_GOT_TLSGD16.
- Use R_DTPREL unconditionally for DTPREL relocations, removing
R_RELAX_TLS_LD_TO_LE_ABS (PPC32 was the only user).
- Move TLS relaxation dispatch from relocateAlloc into relocate,
[2 lines not shown]
NAS-139800 / 25.10.2 / Do not ever apply password aging rules to root (by anodos325) (#18216)
When STIG mode is enabled we enforce password aging rules, among other
things, an expired account will fail internal pam_acct_mgmt calls (even
through unix authentication).
Password aging rules are a separate account control mechanism from
disabling a password (* in the shadow file) and should not be applied
ever to the root account. The proper STIG mode configuration should be
having password disabled for root, but never allowing the account to age
out. The reason for this is that there are various local processes that
use the root account, and require pam_acct_mgmt to succeed: for example,
cronjobs will login() as root to perform tasks.
This commit ensures that the root account will never have password aging
rules applied.
Original PR: https://github.com/truenas/middleware/pull/18213
Co-authored-by: Andrew Walker <andrew.walker at truenas.com>
NAS-139800 / 26.0.0-BETA.1 / Do not ever apply password aging rules to root (#18213)
When STIG mode is enabled we enforce password aging rules, among other
things, an expired account will fail internal pam_acct_mgmt calls (even
through unix authentication).
Password aging rules are a separate account control mechanism from
disabling a password (* in the shadow file) and should not be applied
ever to the root account. The proper STIG mode configuration should be
having password disabled for root, but never allowing the account to age
out. The reason for this is that there are various local processes that
use the root account, and require pam_acct_mgmt to succeed: for example,
cronjobs will login() as root to perform tasks.
This commit ensures that the root account will never have password aging
rules applied.
