X86: Mark EFLAGS clobbers dead in global base register setup (#229337)
Avoid relying on later recomputation of dead flags.
Co-authored-by: Claude Opus 5 <noreply at anthropic.com>
[AMDGPU] Remove unused functions (NFC) (#230382)
AMDGPULegalizerInfo::getLDSKernelId: The last caller was removed on
October 7, 2026 in commit d55fca44d4bb454a573b8338653fbb497c1b0277.
AMDGPUPALMetadata::setFromLegacyBlob: The last caller was removed on
October 7, 2026 in commit d55fca44d4bb454a573b8338653fbb497c1b0277.
AMDGPUNextUseAnalysisImpl::getRelativeLoopDepth: The last caller was
removed on October 7, 2026 in commit
d55fca44d4bb454a573b8338653fbb497c1b0277.
Assisted-by: Antigravity
LiveVariables: Only visit tracked physical registers (#230151)
Keep a bitvector of physical registers with a recorded def or use in
the current block. Register mask handling, the end of block scan, and
the per-block reset now only visit those registers instead of every
register. This is significant for targets with many registers, such as
AMDGPU.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[LV] Tidy up early bail outs related to runtime checks (#228077)
There was no debug or error reporting when bailing out due to proving at
compile time that we will fail the SCEV checks. I've added debug and a
report for this. Also, the early bail out for runtime memory checks has
no corresponding test and I cannot find any test that breaks when I
remove it. I also cannot expose this code path when building the LLVM
test suite, so I've removed it as dead code.
systm.h: Remove unused <sys/kpilite.h>
It only contains sched_pin_lite() and sched_unpin_lite(), which have
been unused in-tree for the past 8 years, and were only briefly used
between 6573d7580b85 ("epoch(9): allow preemptible epochs to compose")
and a760c50c9ea7 ("With epoch not inlined, there is no point in using
_lite KPI. (...)").
Additionally, these functions are redundant with the existing
sched_pin() and sched_unpin() in <sys/sched.h>, which are already
themselves inline functions. The only difference is that the
sched_*_lite() ones do not require the full definition of 'struct
thread', which may have been useful to circumvent namespace pollution.
That problem, if it materializes again, could be quickly circumvented
without this trickery by the use of non-inline functions, or using
inline functions referencing a variable filled at kernel startup with
the desired offset. The trickery of using offsets computed at
compile-time appears necessary only in the case of extremely performance
[7 lines not shown]
Revert "interfaces: the PPP uptime option no longer exists"
This reverts commit b4cca4ef5a7e9ceb8c9fa373b3fe141aefd7cefd.
Meh: apparently all of this works but is never read.
[libc][NFC] Format CMake files under libc/ (#228527)
Run libc/utils/cmake_format.py across libc/ to format CMake files
modified since commit 8969ae16e065.
Assisted-by: Automated tooling, human reviewed.
py-sphinxfeed-lsaffre: updated to 0.3.7
0.3.7
20190315 : Support Python 3 (by using feedgen instead of feedformatter). feed_description is no longer optional.
new config variable feed_field_name to change the name of the metadata field to use for specifying the publication date.
don't publish items whose publication datetime is in the future.
respect use_dirhtml option from rstgen when calculating the url
20240530 : add support to write ATOM instead of RSS.
20240601 : look for two new fields category and tags in the page metadata and if either field or both is present, call the feedgen.FeedEntry.category() method to add <category> elements to the feed item. The difference between category and tags is that the category of a blog post may contain whitespace while the tags metadata field is a space-separated list of tags, so each tag must be a single word. Both the category and each tag will become a <category> element in the feed item.
20240718 : merged 7 commits with minor fixes and config updates from pull request suggested by JWCook
20240720 : The message "Skipping %s, publish date is in the future" is now logged at level INFO instead of WARNING because we don't want the sphinx-build -W to fail in this situation.
20240720 : Removed dependency from atelier because it's easier to call subprocess.check_output() directly here.
20240722 : Support additional timestamp formats (any format supported by dateutil)
20240728: Add feed_entry_permalink option to set a permalink GUID for each feed entry. If a guid value is found in the metadata, that will be used; otherwise, a new one will be generated based on the entry URL. Defaults to False, in which case the entry URL will be used as a non-permalink ID. Applies to both Atom and RSS feeds.
20260325: Add urn:uuid: prefix to permalink GUIDs so they validate as a full URL.
20260325: Handle trailing slashes in feed_base_url
www/pomerium-envoy-custom: update to 1.37.0.20261001
Update to envoy-custom commit 8b998d0f6ff3, which moves the bundled
Envoy from 1.38.2 to 1.38.5, as required by pomerium 0.33.4.
While here, link the envoy binary as a position-independent
executable so that it benefits from ASLR.
net-mgmt/smartctl_exporter: update to 0.15.0
Upstream's go.mod now declares go 1.26, and Go 1.23 and later only
import vendored packages that are listed in vendor/modules.txt. Ship
a generated files/modules.txt and install it in post-extract, and add
a generate-modules-txt maintenance target to regenerate it together
with GH_TUPLE.
Fix the rc.d script:
- smartctl_exporter_syslog is now evaluated with checkyesno; any
non-empty value, including NO, used to enable syslog.
- Quote the device exclude regexp, so that shell metacharacters
such as ( and | no longer break the command line.
- Quote the entries of smartctl_exporter_devices, so that a device
type can be given after a semicolon ("/dev/mfi0;megaraid,1").
While here, set the version reported by the binary and by the build
info metric, and document smartctl_exporter_args.
[2 lines not shown]
py-sphinx-autodoc-typehints: updated to 3.13.9
3.13.9
Fix the forward-reference warning when documenting NumPy's clip by resolving generic parameters declared in stub signatures.
[libc][CI] Add CMake format check to code-format-helper (#228526)
Added CMakeFormatHelper to llvm/utils/git/code-format-helper.py so the
existing GitHub Actions code formatting workflow checks modified CMake
files under libc/ using libc/utils/cmake_format.py.
When formatting issues are found, both the GitHub Actions log and the
automated pull request comment display the exact command to fix the
files in-place alongside the command to preview the diff locally.
Updated libc/utils/cmake_format.py so --dry-run --diff emits only the
unified diff on stdout and exits non-zero on lexer or file errors.
Assisted-by: Automated tooling, human reviewed.
CodeGen: Avoid re-sorting idx2MBBMap when inserting a block into SlotIndexes (#230374)
insertMBBInMaps appended the new block's start index and then re-sorted
the whole map. Renumbering preserves the order of existing entries, so
the map is still sorted and the new entry can be inserted at its sorted position.
Splitting N critical edges paid an O(B log B) sort per split. On
gcc-c-torture compile/20001226-1.c, which has one PHI with ~4K incoming edges, this
was 1/3 of PHIElimination's time.
Instructions retired for llc -O3 on x86_64, varying the number of comparisons in the
test (4k is the original):
input PHIElim before PHIElim after total before total after
1k 326M 224M (-31%) 1.34G 1.24G (-7.5%)
2k 1.27G 0.89G (-30%) 4.25G 3.84G (-9.7%)
4k 4.91G 3.28G (-33%) 12.5G 10.9G (-13.1%)
8k 19.3G 12.8G (-34%) 38.8G 32.2G (-16.8%)
16k 76.2G 50.1G (-34%) 139.2G 113.1G (-18.8%)
[7 lines not shown]
interfaces: wait for parent up as well
This needs more work but for now just do what we already do
while wating for the PPP device to come up: wait for the parent
as well as some drivers may take the parent down for multiple
seconds.
Ideally dialing should be deferred to after bootup which we're
already working on... 30 seconds total delay for non-functional
situation is already a lot.
PR: https://forum.opnsense.org/index.php?topic=52824.0
[mlir][ArmNeon] Add pack/mmt4d path to f32 linalg.matmul integration test (#225063)
This PR adds a `linalg.pack -> linalg.mmt4d -> linalg.unpack` variant to
ArmNeon's f32 `linalg.matmul` integration tests, mirroring
`matmul-i8.mlir`.
NEON has no instruction that multiplies two f32 matrices in one go, only
[`fmla`](https://support.arm.com/documentation/ddi0602/2026-06/SIMD-FP-Instructions/FMLA--vector---Floating-point-fused-multiply-add-to-accumulator--vector--?lang=en),
so the inner tile is `4x4` and each `vector.contract` lowers to outer
products. The accumulator is f32.
Also simplified `ArmSVE/pack-unpack-mmt4d.mlir`'s mmt4d tiling to match,
i.e., one `tile_using_for` call instead of two.
---------
Signed-off-by: Federico Bruzzone <federico.bruzzone.i at gmail.com>
[CIR][NFC] Remove MissingFeatures::hip (#229001)
Following #228377 there are no more uses of MissingFeatures::hip, so
remove it.
Signed-off-by: Steffen Holst Larsen <sholstla at amd.com>
[libc] Fix sigaltstack with SS_DISABLE (#230053)
POSIX.1-2024 (IEEE Std 1003.1-2024) states in the DESCRIPTION section
for sigaltstack: "If it is set to SS_DISABLE, the stack is disabled and
ss_sp and ss_size are ignored."
Previously, sigaltstack unconditionally checked that ss_size was at
least MINSIGSTKSZ. This caused valid calls that disable an alternate
signal stack with ss_size = 0 and ss_sp = nullptr to erroneously fail
with ENOMEM.
Only validate ss_size against MINSIGSTKSZ when SS_DISABLE is not set.
Added SigaltstackDisableStack unit tests and verified invalid stack
combinations. Also updated file headers in the touched files.
Assisted-by: Automated tooling, human reviewed.
[HIP] Compute kernel handle dso_local as for a variable (#229060)
The host-side kernel handle is a global variable, but getKernelHandle
copied dso_local from the device stub while the stub was still a
function declaration. emitDeviceStub then updated the handle's linkage,
but not its dso_local. As a result, dso_local followed the rules for
function declarations rather than those for the handle:
- Under PIE, and with -fno-plt or -fno-direct-access-external-data in
static builds, defined handles were not dso_local, though a definition
in an executable can't be preempted. Every reference to them went
through the GOT.
- With static -fno-plt, a declared handle was not dso_local, though data
can use a copy relocation. -fno-plt only affects calls.
- On MinGW, a declared handle was dso_local, though a variable may be
auto-imported from a DLL.
Compute dso_local with CGM.setDSOLocal when the handle is created and
again once emitDeviceStub gives it its final linkage. The result is what
[5 lines not shown]
