[AMDGPU] Add more known bits simplifications to RegBankCombiner (#238736)
These seem to be beneficial with no drawback.
Reboot from #141591
Adding the full set of KB simplifications doesn't always help.
`redundant_or` in particular causes a few small regressions in some
tests. As I am not focused on GISel as much right now I haven't dug too
deep into what needs to be done to enable all of them (and I am not sure
the effort is worth it).
[libc] Use a syscall wrapper for clock_settime
This PR move clock_settime behind the centralized syscall wrappers, following libc/docs/dev/syscall_wrapper_refactor.md.
[libc] Use a syscall wrapper for clock_gettime
This PR move clock_gettime behind the centralized syscall wrappers, following libc/docs/dev/syscall_wrapper_refactor.md.
[BinaryFormat] Update ELF machines from latest gABI draft (#236171)
I took the meaning as specified in the gABI as readelf name and assigned
new architecture names from the lower-case EM_ macro names. I also
replaced some "EM_*" readelf names with the gABI readable expansion.
net-mgmt/nagios4: Security update 4.5.12 => 4.5.14
This release fixes many vulnerabilities.
Changelog:
https://www.nagios.org/projects/nagios-core/4x/
While here, drop SourceForge from MASTER_SITES.
PR: 300388
Approved by: osa, vvd (mentors, implicit)
MFH: 2026Q4
[GlobalISel] Make m_OneUse ignore debug uses; remove m_OneNonDBGUse (#237070)
The Machine IR `m_OneUse` matcher currently counts `DBG_VALUE` uses. A
debug-only use can therefore block any combine that requires one
ordinary
use and make generated code depend on `-g`. In `matchCtls`, for example,
this AArch64 GlobalISel input emits one `cls` instruction with `-g0`,
but
`eor`/`clz`/`sub` with `-g`:
```c
int cls_add(int x) {
int sign = x >> 31;
int flipped = x ^ sign;
return __builtin_clz(flipped) - 1;
}
```
This patch defines `m_OneUse` in terms of `hasOneNonDBGUse`, removes the
[21 lines not shown]
[mlir][ODS] Include headers required by generated definitions
Generated op, attribute and type definitions use C++ constructs that are not declared by the headers included by the generated declarations.
They therefore relied on the surrounding source file to include these headers before including the definitions.
This PR makes the definitions emit `#include` directives for these headers at the start of the `GET_OP_CLASSES`, `GET_OP_DEFS_<N>` and
`GET_{ATTR,TYPE}DEF_CLASSES` sections.
Similar to #236155 but for the definitions file now. A hardcoded list suffices in this case
[CIR] Add cir-offload-merge tool with a combine mode
Nest a host CIR module and its device modules in an offload container.
Add cir.offload.bundle_id to record each module's offload bundle ID, since
modules can share a triple and differ only in target ID.
bnxt_en: update the driver version to 239.1.153.0
bnxt_en driver version has not been updated for
a while, updating the version now so it better
reflects the current state of the driver.
Sponsored by: Broadcom Inc
firewall: migrate remaining miscellaneous advanced settings
Remove the legacy advanced firewall settings page, but retain the
original ACL name. For good reasons this wasn't introduced in
stable/26.7 yet.
[Remarks][Support] Make YAML remark arguments round-trip
The remark serializer writes an argument value with more than one
newline as a literal block scalar. A block scalar has no escapes, so a
value that also held a control character was written with the raw byte,
which strict YAML readers reject. Output::blockScalarString now falls
back to a double-quoted scalar when a literal block cannot hold the
value: a non-printable character (C1 controls, and NEL, LS and PS,
which YAML 1.1 readers take as line breaks), a carriage return, or a
first line that starts with a space. Input accepts either form.
The remark parser took the raw scalar text and stripped only single
quotes, so double-quoted values came back with their quotes and
escapes. Decode scalars with ScalarNode::getValue and report escape
errors. Reject values that decode to a NUL, since the bitstream string
table stores NUL-terminated strings.
Output::blockScalarString always wrote "|", which keeps exactly one
trailing newline. Write "|-" or "|+" when needed. MIR output does not
[3 lines not shown]
