[Flang][OpenMP] Allow `parallel loop` inside of `teams` (#210679)
A missing `parallel_loop` directive in the `nestedTeamsAllowedSet`
currently causes code like the following to report a semantics issue:
```f90
!$omp teams
!$omp parallel loop
do i=1, 10
end do
!$omp end teams
```
This patch makes sure to accept it, since `parallel` is an allowed
construct to be immediately nested inside of `teams`, even when combined
with another construct.
[GlobalISel] Synchronize GISelValueTrackingAnalysis behavior across Legacy and New PM paths (#207013)
This patch aligns the New Pass Manager (NPM) implementation of
`GISelValueTrackingAnalysis::run()` with the Legacy pass manager by
dynamically adjusting the maximum search depth based on the optimization
level. This eliminates behavioral discrepancies between the two code
paths, reducing migration risks and ensuring consistent compilation
performance and code generation quality across both code paths.
www/chromium: update to 150.0.7871.128
* 150.0.7871.128
This update includes 7 security fixes. Please see the Chrome Security Page for more information.
[N/A][516987782] Critical CVE-2026-15899: Use after free in CameraCapture. Reported by Google on 2026-05-27
[N/A][523750584] Critical CVE-2026-15900: Use after free in GPU. Reported by Google on 2026-06-14
[N/A][533446300] Critical CVE-2026-15901: Use after free in Network. Reported by Google on 2026-07-10
[N/A][522436154] High CVE-2026-15902: Use after free in Cast. Reported by Google on 2026-06-10
[TBD][531503216] High CVE-2026-15903: Out of bounds read and write in V8. Reported by OpenAI Codex Security (amyb) on 2026-07-06
[N/A][532925350] High CVE-2026-15904: Use after free in Ozone. Reported by Google on 2026-07-09
[N/A][532970574] High CVE-2026-15905: Use after free in Aura. Reported by Google on 2026-07-09
* 150.0.7871.124
This update includes 15 security fixes. Please see the Chrome Security Page for more information.
[N/A][517100492] Critical CVE-2026-15764: Use after free in Ozone. Reported by Google on 2026-05-27
[N/A][518007484] Critical CVE-2026-15765: Use after free in Ozone. Reported by Google on 2026-05-29
[N/A][514010477] High CVE-2026-15766: Uninitialized Use in Skia. Reported by Google on 2026-05-17
[43 lines not shown]
[clang][NFC] move traits to tablegen (#201491)
This patch moves all traits to a tablegen file.
The motivation for this change is a review comment in
https://github.com/llvm/llvm-project/pull/142341 - since then about a
year has passed and we've accumulated 9 standard names that are
maintained separately from their corresponding trait definitions. For
transform type traits we keep the standard names around as well. While
this is still a reasonably low number, it is definitely going to keep
increasing.
rust-beta: update to 1.98.0-beta.5
Currently it doesn't build due to warning = error.
===> Building for rust-1.98.0beta.5
Building bootstrap
warning: linker stderr: ld: /usr/pkgsrc/wip/rust-beta/work/rustc-beta-src/build/bootstrap/debug/deps/librustix-095bb558e8cb6f26.rlib(rustix-095bb558e8cb6f26.rustix.b0b38a2615679391-cgu.1.rcgu.o): in function `rustix::backend::io::syscalls::dup3':
rustix.b0b38a2615679391-cgu.1:(.text._RNvNtNtNtCsfazM32Pycft_6rustix7backend2io8syscalls4dup3+0x44): warning: reference to compatibility dup3(); include <unistd.h> to generate correct reference
ld: /usr/pkgsrc/wip/rust-beta/work/rustc-beta-src/build/bootstrap/debug/deps/librustix-095bb558e8cb6f26.rlib(rustix-095bb558e8cb6f26.rustix.b0b38a2615679391-cgu.2.rcgu.o): in function `rustix::backend::fs::syscalls::fstatvfs':
rustix.b0b38a2615679391-cgu.2:(.text._RNvNtNtNtCsfazM32Pycft_6rustix7backend2fs8syscalls8fstatvfs+0x39): warning: reference to compatibility fstatvfs(); include <sys/statvfs.h> to generate correct reference
|
= note: `#[warn(linker_messages)]` on by default
warning: linker stdout: ld: /usr/pkgsrc/wip/rust-beta/work/rustc-beta-src/build/bootstrap/debug/deps/librustix-095bb558e8cb6f26.rlib(rustix-095bb558e8cb6f26.rustix.b0b38a2615679391-cgu.1.rcgu.o): note: the message above does not take linker garbage collection into account
ld: /usr/pkgsrc/wip/rust-beta/work/rustc-beta-src/build/bootstrap/debug/deps/librustix-095bb558e8cb6f26.rlib(rustix-095bb558e8cb6f26.rustix.b0b38a2615679391-cgu.2.rcgu.o): note: the message above does not take linker garbage collection into account
error: `bootstrap` (bin "rustdoc") generated 2 warnings
error: warnings are denied by `build.warnings` configuration
warning: build failed, waiting for other jobs to finish...
[4 lines not shown]
[flang][PFT-to-MLIR] reset Evaluation blocks between entry-point passes (#210681)
A subprogram with an alternate ENTRY is lowered by walking the shared
PFT once per entry. Evaluation::block is populated during each walk
(top-level createEmptyBlocks and inside wrapUnstructuredConstruct's own
createEmptyBlocks), but the second pass previously inherited stale
pointers into the first entry's function/wrap regions. For a wrappable
IfConstruct nested inside a structured container, the entry block that
genFIR(IfConstruct) starts before creating its scf.execute_region then
sent the builder into the previous entry's region, and the wrap plus its
inner load ended up in the wrong func:
subroutine foo(a)
integer a
entry bar(a)
if (a .eq. 1) then
if (a .ne. 3) stop
end if
end subroutine
[10 lines not shown]
[libc++] Bring std::{any,all,none}_of tests up to current standards (#209266)
The tests for these algorithms were minimal, didn't test all iterator
categories, and the constexpr coverage didn't follow our current
practice. This patch brings all three tests (which are very similar) up
to our current standards.
Assisted by Claude
[PowerPC]optimize the epilogue for restore non volatile cr fields (#202339)
For AIX and ELFv2 ABI,
1. When we only spill one non-volatile CR field , using one
mfocrf/mtocrf instruction.
2. when spill two or more non-volatile CR fields, using one mfcr/mtcr
instead of multi mfocrf/mtocrf instructions
[libc++][utils] Fix LIT `%if` substitution support (#209358)
Update the applySubstitutions call in `libcxx/utils/libcxx/test/format.py` to match the
change to `llvm/utils/lit/lit/TestRunner.py` done in 1041a9642ba0.
NAS-141814 / 27.0.0-BETA.1 / Report fine-grained app job progress from docker compose events (#19343)
## Motivation
App install/update/upgrade/pull jobs currently jump between fixed
progress milestones — on upgrade, everything between 50% and 100% (the
entire image pull and container recreation, i.e. most of the wall-clock
time) happens silently.
## Changes
- `compose_action()` accepts an optional `progress_callback`. When set,
it runs `docker compose --progress=json` with line-streamed stderr, and
the new `ComposeProgressTracker` aggregates per-layer download/extract
bytes and container/network events into a monotonic fraction with
descriptions like `Pulling app images (27.35 MiB / 69.03 MiB)`. Wired
into install, update/redeploy, upgrade, custom app create, and
`app.pull_images`, each mapped into its own band of the job's progress.
- Child job progress now proxies into parent jobs via
[35 lines not shown]
Bring back up_generate_addpath_all() using the rib entry queue
add-path send all can take a fair amount of shortcuts compared to the
other add-path send modes. The rib entry queue (struct pq_entry) holds
all the information to update the adj-rib-out.
For general updates just walk the pq list and insert / withdraw all
paths. A path can only be once on the list so the code just needs to
walk it and call up_process_prefix for updates. If up_process_prefix()
returns UP_FILTERED or UP_EXCLUDED then try to withdraw the prefix. This
uses the same codepath as for any withdraw in the queue.
Tested on the NLNOG ring looking glass server.
OK tb@
[libc++][test] Fix build failure from typo in #171785 (#210552)
If `__STDCPP_DEFAULT_NEW_ALIGNMENT__` is not defined, these tests will
fail to build due to a typo that was added in #171785.
[libc++] Run macOS CI on self-hosted runners instead of Github ones (#210124)
This should increase our capacity and allow better turn around times,
and potentially unblock additional test coverage.
Note that this change implies that the self-hosted runners provide a
version of Xcode that is supported by libc++ (the latest released one),
which is currently the case.
