www/py-django-q2: Fix build after devel/py-uv-build update
Patch pyproject.toml to stretch out devel/py-uv-build version range.
PR: 298327
Approved by: osa, vvd (Mentors, implicit)
[CMake] Infer dependency-only projects from the cache
LLVM_ENABLE_PROJECTS historically treats projects enabled to satisfy another
project's dependency the same as projects selected by the user. Consequently,
implicit projects attach their complete build, install, and test suites to
LLVM's aggregate targets.
Keep the cache entry as the user-requested project roots and use the normal
LLVM_ENABLE_PROJECTS variable as the effective dependency closure. Projects in
the effective list but not the cache entry are configured with
EXCLUDE_FROM_ALL. Normalize the special all value before comparing the two
sets.
This makes Flang's MLIR and Clang dependencies dependency-only without a
second project collection. It also applies the same rule to Clang when it is
added for LLDB. Forward the cached roots to cross-compilation and bootstrap
configurations so implicit projects do not become explicit in nested builds.
Let MLIR own its dependency-only test policy: configure its complete test tree
[13 lines not shown]
[CIR][CMake] Configure MLIR as a dependency-only project
ClangIR requires MLIR, but enabling CIR currently requires users to list MLIR
explicitly in LLVM_ENABLE_PROJECTS. That also attaches all MLIR build, install,
unit-test, and lit targets to the corresponding LLVM aggregates.
When Clang is selected and CLANG_ENABLE_CIR is enabled, append MLIR to the
effective LLVM_ENABLE_PROJECTS list. The common project setup compares that
list with the cached user selection, so an explicit MLIR selection retains its
normal behavior while an implicit selection is configured with
EXCLUDE_FROM_ALL.
This makes MLIR targets available for CIR dependency resolution without adding
MLIR tests to check-all. Keep the existing standalone ClangIR restriction and
do not configure MLIR when CIR is disabled.
Validation:
- Configured Clang with CIR and implicit MLIR test support.
- Configured Clang and MLIR explicitly with CIR and tests enabled.
[6 lines not shown]
[AArch64] Form CCMP for CBB and CBH
AArch64ConditionalCompares forms CMP/CCMP chains to transform patterns
such as
Head Head
/ | CmpBB
/ | / |
| CmpBB => / |
| / | Tail |
| / | | |
Tail | | |
| | | |
... ... ... ...
where Head is terminated by a conditional branch and CmpBB contains
a cmp + conditional branch.
We usually try to split any fused conditional branches to be able to
[8 lines not shown]
[AArch64][CMPBR] Fix splitting of CBB/CBH instructions into ext + cmp (#221112)
We falsely split CBB/CBH instructions by explicitly extending the
second register operand instead of the first one, leading to the
following, wrong codegen:
cbh $wn, $wm, cc, trgt => sxth $wt, $wm
cmp $wn, $wt, cc, sxth
Correct is
cbh $wn, $wm, cc, trgt => sxth $wt, $wn
cmp $wt, $wm, cc, sxth
since cmp with extended register extends it's second, not its first
operand.
[MLIR][Linalg] Update transform tests for strict properties (#222184)
Update recently added vectorization tests to use the custom assembly
syntax.
Strict Transform dialect properties no longer parse inherent attributes
from the generic attribute dictionary.
These tests landed concurrently with the strict-properties migration.
Assisted-by: Codex
[libc][netdb] Add AI_* family of constants. (#221360)
* Provide the values for `AI_*` flags that are passed in `ai_flags`
field of `addrinfo`
structure to `getaddrinfo` calls.
* Reference some of those constant in a placeholder unittest. Rename it
to `getaddrinfo_test`
to clarify its scope (we'll likely be using different test files for
other netdb.h functions).
Instead of writing partial-segments synchronously when sync is requested,
write them async, but wait for vp->v_numoutput to drop to zero if the
calling semantics require it. That way, even if we might have to wait,
nobody else is required to wait with us.
[CIR][NFC] Tighten the direct-offset test checks
The checks pinned the byte-8 literal and little else, and the CIR side only
checked signatures. They now chain the argument through the stride into the
store, on the callee and caller side both.
Assisted-by: Cursor / claude-opus-5
[clang][docs] Adopt the furo theme used by llvm and libc (#214869)
This change moves the static assets into utils/docs/llvm_sphinx, and
centralizes some of the furo theme logic there.
It then configures furo from clang/docs/conf.py and
clang/analyzer/docs/conf.py.
The temporary preview for the site is here:
https://clangdocs.staging.reidkleckner.dev/after/clang/docs/
The RFC is here:
https://discourse.llvm.org/t/rfc-use-furo-theme-for-clang-docs/91505/7
I plan to wait until at least Aug 13 before merging to gather more
feedback.
[docs] Remove TOCs from Clang docs to prepare for Furo migration (#214868)
This is a mechanical change generated by
`utils/docs/remove_page_tocs.py`. In case of conflicts, which are
likely, due to the ongoing markdown migration (#201242), this script can
be re-run to regenerate the change. I'm creating a separate PR for it to
minimize the diff on the functional changes for the furo PR.
sysutils/slurm-wlm: Update 26.05.2 => 26.05.4
Changelog:
https://github.com/SchedMD/slurm/blob/slurm-26.05/CHANGELOG/slurm-26.05.md
- Remove obsolete downstream HDF5 patches; the corresponding changes are
no longer required with the new upstream release.
- Drop now-obsolete portions of patch-configure, substantially reducing
the downstream configure patch.
- Rebase the existing FreeBSD conmgr patch against the new upstream
sources.
- Add a missing <signal.h> include to the pack_priority_factors unit
test required for the test suite to build on FreeBSD.
PR: 298317
Security: CVE-2026-65107
Security: CVE-2026-65108
Security: CVE-2026-65109
Security: CVE-2026-65138
[7 lines not shown]
[libc][bazel] Allow building with -DLIBC_FULL_BUILD (#218992)
This PR defines a flag `--@llvm-project//libc:build_mode` that
configures LLVM-libc to build with full-build flags. This is only
compatible with clang at the moment, since it relies on the
`-nostdlibinc` flag.
This PR contains the logic for LLVM-libc full build in Bazel. A largely
AI generated follow-on PR has `libc/BUILD.bazel` changes for building
libc targets in full-build mode:
https://github.com/llvm/llvm-project/pull/218993.
[libc][bazel] Add a repo with linux kernel UAPI headers (#216867)
This PR exposes a target `@linux_uapi//:linux_uapi_headers` that points
to a local directory configured by the `LINUX_UAPI_INCLUDE_DIR`
environment variable. Linux UAPI headers are required to support libc's
`FULL_BUILD` configuration, which uses `-nostdlibinc` and thus requires
a copy of linux kernel headers.
sysutils/slurm-wlm: Update 26.05.2 => 26.05.4
Changelog:
https://github.com/SchedMD/slurm/blob/slurm-26.05/CHANGELOG/slurm-26.05.md
- Remove obsolete downstream HDF5 patches; the corresponding changes are
no longer required with the new upstream release.
- Drop now-obsolete portions of patch-configure, substantially reducing
the downstream configure patch.
- Rebase the existing FreeBSD conmgr patch against the new upstream
sources.
- Add a missing <signal.h> include to the pack_priority_factors unit
test required for the test suite to build on FreeBSD.
PR: 298317
Security: CVE-2026-65107
Security: CVE-2026-65108
Security: CVE-2026-65109
Security: CVE-2026-65138
[5 lines not shown]
[SandboxVec][Scheduler] Reinsert deferred ready nodes to the ready list (#222054)
Up until now if trySchedule() failed, the ready instructions would be
removed from the ready list for no good reason.
This patch fixes this and reinserts the deferred nodes to the ready
list.
This also helps reduce the scan for ready instructions in trySchedule().
