databases/postgresql19-*: Update to 19.0
First production release of the 19 series.
This release introduces the REPACK (CONCURRENTLY) command so users can
optimize tables for their current workload without disruption to ongoing
operations. PostgreSQL 19 gives users better control over plan stability
and query performance with the new pg_plan_advice extension. Developers
will find many delightful features in this release, from support for
"read-your-writes" consistency on standbys to "get or create" behavior
that saves a network round trip.
Upgrading from 18 or earlier requires a dump/restore or pg_upgrade.
Release notes: https://www.postgresql.org/docs/19/release-19.html
(cherry picked from commit 5fa58ac8856ff5bbf8d6b65a0769cdba11e336ed)
databases/postgresql1[45678]-*: Update to latest patch releases
Update to 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 53 CVEs and
a large number of other bugs.
A dump/restore is not required, but some indexes may be corrupt and
should be rebuilt with REINDEX after updating:
- btree indexes on bpchar columns declared without a length
(CHAR(n) is not affected)
- GiST indexes using gist_trgm_ops (contrib/pg_trgm)
- GIN indexes and TOAST-table indexes, if corruption is suspected
For 17 and 18, existing incremental backups should not be trusted.
Take a new full backup after updating and base subsequent
incremental backups on that.
Release notes: https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/
Security: 1a672925-de93-11f1-9824-6cc21735f730
[2 lines not shown]
databases/postgresql19-server: Update to 19RC1
The PostgreSQL Global Development Group announces that the first release
candidate of PostgreSQL 19 is now available for download. As a release
candidate, PostgreSQL 19 RC 1 will be mostly identical to the initial
release of PostgreSQL 19, though some more fixes may be applied prior to
the general availability of PostgreSQL 19.
To upgrade to PostgreSQL 19 RC 1 from earlier versions of PostgreSQL,
you will need to use a major version upgrade strategy, e.g. pg_upgrade
or pg_dump / pg_restore. For more information, please visit the
documentation section on upgrading:
https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/
(cherry picked from commit 0ee810cf51b3110956e0ac1076a2ebb6f7de320f)
[mlir][shape] Don't crash on poison operands in folders (#226671)
Several shape folders used an unchecked `llvm::cast` on their folded
operands, assuming any non-null attribute was a `DenseIntElementsAttr`
(or `IntegerAttr`). A `ub.poison` operand folds to `#ub.poison`, so
these casts asserted.
The folders now check attribute types before accessing their values and
propagate poison where appropriate.
- `ConcatOp`, `NumElementsOp`, `SplitAtOp` and `ToExtentTensorOp` fold
to poison when an operand is poison.
- `CstrBroadcastableOp` (and its `hasAtMostSingleNonScalar` helper) no
longer crashes; poison is treated like a non-constant operand there.
`NumElementsOp`, `SplitAtOp` and `ToExtentTensorOp` weren't in the
issue; I found them while fixing the reported ones.
Part of #226067 (the affine and scf cases are not addressed here).
Assisted-by: Claude
[Affine] Parallelize loops with MemoryEffects::Free ops. (#172388)
It seems that operations with just MemoryEffects::Free should not
prevent parallelization.
18761 make: targets with '%' in their name are rebuilt on every run
Reviewed by: Andy Fiddaman <illumos at fiddaman.net>
Reviewed by: Bill Sommerfeld <sommerfeld at hamachi.org>
Approved by: Gordon Ross <gordon.w.ross at gmail.com>
NAS-145324 / 27.1.0 / Check the resolved path in filesystem permission changes (by bmeagherix) (#20271)
The path checks of filesystem.chown, filesystem.setperm and
filesystem.setacl compared filesystem.stat's realpath, which keeps ".."
components for anything that is not itself a symlink, and matched
prefixes without a component boundary. Check os.path.realpath() of the
path instead, and compare whole path components.
Also fix the schema name in the "Must be an absolute path" error.
Original PR: https://github.com/truenas/middleware/pull/20267
Co-authored-by: bmeagherix <118192357+bmeagherix at users.noreply.github.com>
NAS-145323 / 27.1.0 / Only accept a report file name in audit.download_report (by bmeagherix) (#20273)
audit.export creates each report directly in the user's report
directory, so report_name must be a single file name.
Original PR: https://github.com/truenas/middleware/pull/20266
Co-authored-by: bmeagherix <118192357+bmeagherix at users.noreply.github.com>
[InstCombine] Rewrite foldICmpCommutative to switch on the op0 opcode (#243249)
foldICmpCommutative is called twice for every icmp, once for each operand
order, and tries a sequence of folds that each require Op0 to be a particular
operator: a GEP, a select, a min/max or abs call, an add, an and/or, a
division, or a shift. Each fold only finds out after running its own pattern
match.
Turn the sequence into a switch on Op0's opcode. Every fold in this function
is keyed on that opcode and the keys are disjoint, so the switch only skips
folds that cannot apply. No fold is added or removed, and folds for the same
opcode keep their original order. `Operator::getOpcode` is used so that
constant expressions dispatch the same way PatternMatch treats them.
The switch also makes the dispatch structure explicit, so new folds added here
are naturally placed under the opcode they require. The opcode guards in
visitICmpInst and its other helpers from the first version of this PR will be
evaluated separately.
[7 lines not shown]
[LV] Add tests for interleave group and replicated load addresses (NFC). (#244355)
Add tests for
* the cost of address computations of interleaved store and load groups,
* abs of the IV used as interleave group address,
* replicated loads used as address via blends,
* a forced scalar address computation VPlan narrows to a single scalar.
[InstCombine] Fix infinite loop when simplifying copysign (#243432)
Only report a change when the copysign sign operand actually changes.
Otherwise, demanded FP-class simplification through a loop PHI can keep
revisiting the same instructions without changing the IR.
Assisted-by: OpenAI Codex
[OCaml] Add FMaximumNum and FMinimumNum to AtomicRMWBinOp.t (#240894)
`LLVMAtomicRMWBinOp` gained `LLVMAtomicRMWBinOpFMaximumNum` and
`LLVMAtomicRMWBinOpFMinimumNum`, but the OCaml variant
`AtomicRMWBinOp.t` stops at `FMinimum`, so OCaml code cannot build these
operations. `build_atomicrmw` passes the constructor index straight to
`LLVMBuildAtomicRMW`, so the two lists have to stay in the same order.
This adds the two constructors at the end of the variant, in the C
order.
Assisted-by: Mistral Vibe
[flang][OpenMP] Do not register DECLARE_REDUCTIONs in METADIRECTIVEs
Since declarative METADIRECTIVEs are not handled yet, they shouldn't
produce any side-effects. Specifically DECLARE_REDUCTION directives
should not actually declare anything.
This PR eliminates the actual declaration of the reduction-identifier
associated with a DECLARE_REDUCTION in a METADIRECTIVE.
bhyve/riscv: fix PCIe FDT interrupt-map entry stride
In bhyve arm64, each PCIe interrupt-map entry spans 10 cells because the
ARM GIC specifies #interrupt-cells = 3. On RISC-V, the APLIC uses
#interrupt-cells = 2, so each entry spans only 9 cells.
When the PCIe FDT code was originally adapted from arm64, the property
allocation size and cell assignments were reduced to 9 cells per entry,
but the loop multiplier retained the 10-cell stride. This caused the
interrupt-map array to be packed incorrectly with gaps, breaking PCI
interrupt routing in guest operating systems and overflowing the
allocation by 16 cells.
Correct the loop stride to 9 cells so the interrupt map is properly
formed.
Reviewed by: jrtc27
Fixes: 7ab1a32cd43c ("bhyve/riscv: Initial import")
MFC after: 3 days
[3 lines not shown]
[flang][OpenMP] Handle declarative METADIRECTIVES more carefully
Diagnose declarative METADIRECTIVEs with executable variants as errors.
A METADIRECTIVE is considered executable if it contains at least one
executable variant. Mixing declarative and executable variants is not
supported.
There are several things that can appear in either the specification part
or in the execution part in a Fortran program unit. METADIRECTIVEs are
one example, and there is already code that tries to canonicalize then,
i.e. move them into the execution part if they are considered executable
and are at the end of the specification part.
In fact, the entire tail of the specification part is moved into the
execution part if it could be considered executable.
Since OmpMetadirectiveDirective is an allowed member of a specification
part, the parser will preferentially insert METADIRECTIVEs into the
specification part even if they are executable according to the above
definition.
[7 lines not shown]
Revert "bhyve/riscv: fix PCIe FDT interrupt-map entry stride"
Thanks to past me's foolish choice not to alter the commit message such
that none of its lines start with a #, Git got very confused the
cherry-pick and included its own commented-out instructions. Reverting
to re-land with a fixed body.
This is a direct commit to stable/15.
This reverts commit 69f76efd01a72fe0d6cb68442d2c15d3174a268f.
[clang-format] Break and align items after trailing-comma __VA_OPT__ (#240902)
When `__VA_OPT__(..., )` (or `__VA_OPT__(,)`) ends with a top-level
comma inside an enum, braced list, parameter list, or expression (for
example when migrating unnamed variadic macros from the non-standard `,
##__VA_ARGS__` extension to C++20 `__VA_OPT__(__VA_ARGS__, )`), its
closing `)` acts as an item separator. Previously, `clang-format` did
not recognize the trailing comma inside `__VA_OPT__`, keeping the
following item on the same line (or continuation-indenting it after
`)`).
Classify the closing `)` of a C/C++ `__VA_OPT__` ending in a top-level
non-operator comma as `TT_TrailingCommaVaOptRParen` and treat it as a
comma separator across token annotation, parameter counting and column
layout, bin-packing, continuation indentation, trailing-comma handling,
and expression grouping.
Before:
[21 lines not shown]
[libc] Add strtof128 stdlib entrypoint. (#243955)
Enable for aarch64, riscv, and x86_64, using the emulated float128 type
in the implementation and helper tests.
The logic for string to float128 conversion is already in
__support/str_to_float.h for the case when long double is quad
precision. It just needed some template updates to enable for float128.
Assisted-by: Automated tooling, human reviewed.
[VPlan] Remove unused VPLane::getKnownLane (NFC) (#244312)
The last callers were removed on November 19, 2026 in commit
39cc2f5728e49e5c8df0acd80fd17985862df9d3.
Assisted-by: Antigravity
[AMDGPU] Remove unused getGPUName and getFeatureString (NFC) (#244311)
The last callers were removed on November 18, 2026 in commit
95f23a1ae335e929987a99521ab7e3e08da54ba4.
Assisted-by: Antigravity
[IR] Remove unused RuntimeLibcallsInfo::darwinHasSinCosStret (NFC) (#244307)
The last caller was removed on November 18, 2026 in commit
3490218b05171319625693a1c0003dbb793a0e76.
Assisted-by: Antigravity
[TableGen] Remove unused InfoByHwMode::makeSimple (NFC) (#244306)
The last caller was removed on November 6, 2026 in commit
7d2b3c904c95f7173b677f6d04eb8fff0c8932b7.
Assisted-by: Antigravity
bhyve/riscv: fix PCIe FDT interrupt-map entry stride
In bhyve arm64, each PCIe interrupt-map entry spans 10 cells because the
ARM GIC specifies #interrupt-cells = 3. On RISC-V, the APLIC uses
#interrupt-cells = 2, so each entry spans only 9 cells.
When the PCIe FDT code was originally adapted from arm64, the property
allocation size and cell assignments were reduced to 9 cells per entry,
but the loop multiplier retained the 10-cell stride. This caused the
interrupt-map array to be packed incorrectly with gaps, breaking PCI
interrupt routing in guest operating systems and overflowing the
allocation by 16 cells.
Correct the loop stride to 9 cells so the interrupt map is properly
formed.
Reviewed by: jrtc27
Fixes: 7ab1a32cd43c ("bhyve/riscv: Initial import")
MFC after: 3 days
[25 lines not shown]
[llvm][vfs] Add Status::isExecutable() (#244339)
Add a query to vfs::Status that returns whether any of the execute
permissions is set, so that clients checking whether a file found
through a VFS is executable don't have to test the permission bits by
hand. Update MSVC toolchain to use the new API.
Unlike sys::fs::can_execute, it does not check whether the current
process is allowed to execute the file.
ZTS: slog_replay_volume_split_*: write with stride_dd (#19917)
slog_replay_volume_split_boundary and slog_replay_volume_split_write
fail on every ubuntu26 CI run since its kernel moved to 7.0.0-43:
the replayed data matches, but no split write was logged or merged.
The tests make one 512K or 768K O_DIRECT write(2) to the zvol with
dd, so that it reaches the zvol as one request and is logged as one
TX_WRITE record split over several log blocks. Ubuntu 26.04's dd is
uutils dd, which reads into a buffer that is not 512-byte aligned.
Kernel 7.0.0-38 let that O_DIRECT write through to the zvol as one
bio; 7.0.0-43 rejects it with EINVAL, as it already did for other
block devices with the default 511 dma_alignment. uutils dd then
clears O_DIRECT and writes again through the page cache, so the zvol
gets 128 or 192 4K bios, each logged as its own small record.
Write with stride_dd -D instead: its buffer is page-aligned, and it
fails rather than retry without O_DIRECT.
[2 lines not shown]
[lldb] Add a Deprecated attribute for settings, to discourage use (#243732)
I want to change all of the lldb-cache-index settings that exist today,
reorganizing them to reflect how I'm growing the DataFileCache system.
Users may have the old settings in their .lldbinit files, and I don't
want those to result in errors. I will mark the old settings Deprecated,
and if they are set, have them set the correct new setting names.
The goal of a deprecated setting is to make it undiscoverable by
accident -- `settings list`, `settings show` will not show the name
unless the full path is given, unless `--include-deprecated` is added.
When it is shown, the setting name will be followed by a deprecation
tag, "(deprecated)". If a user sets a setting with `settings set`, a
warning will be printed that this setting is deprecated - so their
.lldbinit file will give a warning each time it is sourced, but it will
continue to work.
I think the most important thing to consider with this PR are the UI of
all the different ways settings are accessed and viewed. This PR adds a
[128 lines not shown]
[MLIR][PDL][Test] Fix memory leaks in testNullPDLValueArg (#244344)
https://github.com/llvm/llvm-project/pull/228456 added
`testNullPDLValueArg` in `mlir/test/CAPI/pdl.c`, which fails under
LeakSanitizer on the ASan buildbot.
`mlirRewritePatternSetFromPDLPatternModule` and
`mlirFreezeRewritePattern` move the contents out of their input handles
without freeing the heap-allocated containers themselves, and
`FrozenRewritePatternSet` leaves the lowered `OwningOpRef<ModuleOp>`
inside the `RewritePatternSet`. Passing the `MlirRewritePatternSet` as
an unnamed temporary and omitting the destroy calls therefore leaked
`MlirPDLPatternModule` and `MlirRewritePatternSet`.
This PR destroies both `pdlModule` and the intermediate `patternSet`
after freezing. This is the same pattern in `mlir/test/CAPI/rewrite.c`.
Assisted-by: Gemini