lang/v8: Fix fetch by fetching sub-dependencies from GitHub mirror
The +archive tarballs on chromium.googlesource.com are generated on
the fly with the time of the request as the mtime of every entry,
and the generated tarballs are not reproducible, so their size and
checksum change with each download and fetch fails with a size
or checksum mismatch.
To address this, fetch all sub-dependencies with GH_TUPLE from the
unofficial chromium-full-mirror organization on GitHub, which carries
the same commits and produces stable tarballs.
Because the chromium-full-mirror is an unofficial mirror, a new
verify-mirror target is added, which downloads every sub-dependency
from chromium.googlesource.com and compares the extracted tree with
the mirror distfile.
This new target is run as part of "make makesum" so distinfo can only
be generated when comparison passing.
[7 lines not shown]
[CIR] Parse .cir cc1 input and support -emit-cir from it (#228288)
Fill in the Language::CIR path of CIRGenAction::ExecuteAction: register
the ClangIR dialects, parse and verify the main file into a ModuleOp
with MLIR diagnostics routed through CIRDiagnosticHandler, and require
the module's cir.triple to match the target triple. A mismatch is an
error rather than an override, because CIR emitted by -emit-cir has
already been lowered for the target ABI of its own triple.
It is still unclear whether we should disallow any overrides of module
CIRGen attribues. At this point in time, I opt to go with a conservative
approach.
The CIR-to-CIR pipeline is not run, because -emit-cir output has already
been through it and its lowering passes are not idempotent; recording
the pipeline stage on the module is left for a follow-up. Other outputs
still report that ClangIR input is not yet supported.
`registerAllDialects` now registers the LLVM dialect. The data layout
[14 lines not shown]
[MC][ELF] Preserve bits 7:4 of st_other (#228882)
The ELF gABI defines visibility in the low bits of st_other and leaves
the upper bits without a generic meaning [1]. Architecture-specific ELF
extensions use these upper bits. MIPS uses bits 7:4 to identify MIPS16
code symbols with STO_MIPS_MIPS16 (0xf0).
MCSymbolELF currently accepts only bits 7:5, so setting STO_MIPS_MIPS16
triggers an assertion. Expand the storage to preserve bits 7:4 and shift
the adjacent internal flags accordingly.
[1] ELF gABI, Section 5.1, Symbol Table Entry:
https://gabi.xinuos.com/elf/05-symtab.html#symbol-table-entry
Assisted-by: OpenAI Codex
devel/R-cran-rdtools: New port
Provides fast, cached lookup of help topics and aliases across installed,
source, and in-development packages, plus efficient retrieval of parsed 'Rd'
('R' documentation) objects. Per-package indexes are built once and cached,
making repeated retrieval cheap enough to call in a tight loop.
This port is required updating of devel/R-cran-roxygen2.
HBSD: Fix build of emulators/snes9x-gtk
snes9x has some potential format string vulnerabilities, which is caught
by our use of specific compiler flags.
Signed-off-by: Shawn Webb <shawn.webb at hardenedbsd.org>
[LoongArch] Use [X]VSETNEZ.V/[X]VSETEQZ.V for whole-vector zero check (#226814)
Introduce `loongarch_vanynonzero` and `loongarch_vallzero` for checking
wether a vector has any non zero or all of them are zero, which could
simply some vector comparison such as the one below.
Before
```
xvseq.d $xr0, $xr0, $xr1
xvmskltz.d $xr0, $xr0
xvpickve2gr.wu $a0, $xr0, 0
xvpickve2gr.wu $a1, $xr0, 4
bstrins.d $a0, $a1, 3, 2
beqz $a0, .LBB2_2
```
After
```
xvseq.d $xr0, $xr0, $xr1
xvseteqz.v $fcc0, $xr0
[4 lines not shown]
prometheus: update to 3.13.4.
[SECURITY] Bump google.golang.org/grpc to v1.83.1 to fix HTTP/2
DATA frame fragmentation memory exhaustion (GO-2026-6348). #19834
[SECURITY] UI: Update vulnerable npm dependencies. #19834
[BUGFIX] Agent: Ignore unknown WAL record types to allow rolling
back from newer versions. #19814
[BUGFIX] Federation: Fix corruption of float native histograms.
#19679
[BUGFIX] Scrape: Fix failing scrapes of protobuf float histograms
with zero sample, zero and bucket counts, such as the result of
recording rate(x[1m]) over a constant histogram. #19682
nvme: set the controller Timestamp feature
Controllers that report ONCS.TIMESTAMP keep a millisecond clock that the
host is expected to seed
Reviewed by: imp, adrian
Differential Revision: https://reviews.freebsd.org/D59997
nvme: set the controller Timestamp feature
Controllers that report ONCS.TIMESTAMP keep a millisecond clock that the
host is expected to seed
Reviewed by: imp, adrian
Differential Revision: https://reviews.freebsd.org/D59997
nvme: do not complete a command when its Abort is not performed
An Abort completion with cdw0 bit 0 set means the controller did not
abort the command; the command can still complete later. The driver
treated this as aborted anyway: it completed the command itself and
freed the CID. When the controller completed the command later,
the CID may already belong to a new command, so the new command
finished with the old command's status, or the unknown-cid assertion
fired on INVARIANTS kernels. The watchdog also kept sending a new
Abort for the same command every half second while the first one was
still pending.
Reviewed by: imp, adrian
Differential Revision: https://reviews.freebsd.org/D59634
