emulators/es-de: Unbreak after x11-fonts/ubuntu-font update
The recently updated x11-fonts/ubuntu-font has different names for its
*.ttf files. This broke es-de at runtime, because it explicitly wants to
load "Ubuntu-C.ttf", which isn't provided by ubuntu-font anymore.
The port links to "Ubuntu[wdth,wght].ttf" instead to unbreak es-de.
While here, apply the new framework-provided BUILD_RUN_DEPENDS in place
of the custom _BR_DEPENDS variable.
PR: 298815
Approved by: osa, vvd (Mentors, implicit)
[mlir][xevm] Fold xevm.truncf of an xevm.extf round trip (#225875)
A xevm.extf followed by a xevm.truncf through the same pair of formats
returns the value it started from, so the pair can be dropped. Fold it
on the truncf, the way arith::TruncFOp::fold recognizes truncf(extf(a)),
and gate it on APFloatBase::isLosslesslyConvertibleTo of the two formats
the element type attributes stand for.
That gate excludes bf8: it is IEEE-like, so extending a signaling NaN
quiets it and the original value cannot be recovered, which is the same
reason arith does not fold an f8E5M2 round trip. f8 (E4M3, NaN only) and
e2m1 (finite only) do fold.
Mark both ops Pure so the extf left without users is removed and the
pair folds to nothing.
[mlir][xegpu] Distribute three more convert_layout cases to lanes (#222693)
`xegpu-sg-to-lane-distribute` could not lower an `xegpu.convert_layout`
whose effective `lane_layout` changes in a way that moves elements
between lanes. Add one pattern per case found in the workgroup-level
mx-fp GEMM quantize-A kernels, where `#xegpu.slice` layouts of a rank-3
layout meet the rank-2 layouts of `load_nd` and `dpas_mx`:
- fully broadcast source to one row per lane: `vector.extract`
- source broadcast over two lane groups to one row per lane:
`vector.extract` plus two `gpu.shuffle`
- fully broadcast source to one column per lane group:
`vector.deinterleave` plus a select on the lane group
[HTTP][Windows] Apply the configured timeout to WinHttpReceiveResponse (#226172)
`WinHttpSetTimeouts` does not bound the wait inside
`WinHttpReceiveResponse`, which has its own separate
`WINHTTP_OPTION_RECEIVE_RESPONSE_TIMEOUT`.
For example: with the SymStore timeout set to 1s, a server stalling 5s
before responding is not cancelled: `perform()` returns success with a
200 and no body, so lldb handed back a path to a file the response
handler never created.
This fixes `symstore/TestSymStore.py` (test_http_timeout) in swiftlang.
www/bunkerweb: Enable ModSecurity when the module is available
Render the ModSecurity directives only if
ngx_http_modsecurity_module.so is installed, like upstream does for
the stream module. Build www/openresty with the MODSECURITY option to
get it.
Point the remaining paths at their FreeBSD locations, error pages,
assets and rule files were read from /usr/share/bunkerweb.
Sponsored by: Netzkommune GmbH
www/openresty: Add MODSECURITY option
Builds ModSecurity v3 as a dynamic module from the same sources and
with the same configure arguments as the server itself, so it loads
without --with-compat. Off by default.
Setting USE_GITHUB drops the openresty tarball from DISTFILES, so set
it explicitly.
Sponsored by: Netzkommune GmbH
[Github] Install sccache from apt repo (#226019)
Now that we are on ubuntu 26.04 we have sccache 0.13.0 which should be
new enough that everything works.
[lldb][test] Use MKDIR_P in more API test Makefiles (#226157)
Replace `mkdir -p` with `$(call MKDIR_P,...)` in a few API test
Makefiles so they work with the Windows shell.
[Clang] Fix stmtexprs.c to not specify -pedantic (#226161)
Fixes a buildbot failure (llvm-clang-x86_64-sie-ubuntu-fast) where
`stmtexprs.c` didn't specify a C standard, causing `_Static_assert` and
`_Generic` to be flagged as C11 extensions on targets that default to an
older standard.
This removes `-pedantic` from the RUN line because the test does not
test any extension behavior anyway.
Follow-up to #225597.
[AMDGPU] Price only the fmul that fuses into an fadd/fsub as free (#226009)
An fadd/fsub with two fmul operands can fuse with only one of them into
an FMA. Currently they are both priced as if they are fused (i.e. free).
rpki-client: rename valid_x509() to valid_cert()
x509 usually indicates an X509 * argument and cert a struct cert *.
This got changed in the surgery today and valid_cert() is now free,
so we can fix this.
ok claudio
[lldb][Windows] Compare real paths in TestReplaceDLL (#226177)
lldb reports a module's canonical path, which differs from the build
artifact path when the build tree is reached through a subst drive
(`S:\...` vs `C:\S\...`). Compare real paths instead.
Fixes `windows/launch/replace-dll/TestReplaceDLL.py` in swiftlang CI
where we use subst drives.
[clang][OpenMP] Only accept char strings in the message clause (#226080)
Fixes #140338
The `message` clause accepted any character-typed string, checked with
`isAnyCharacterType()`, but everything that consumes it assumes a `char`
string: Sema evaluates it into a `std::string` for the compile-time
diagnostic, and codegen passes it straight to the `const char *`
parameter of `__kmpc_error` and `__kmpc_push_num_threads_strict`. When
the issue was filed this hit the assertion in
`StringLiteral::getString()`. Since #146405 the assert is gone, but the
underlying problem stayed: in C++ a wide literal like `message(L"bar")`
prints `b<NUL><NUL>` as the error text, and with `at(execution)` a
`wchar_t` array is emitted as the runtime's `char *` argument. C was
only spared because `wchar_t` is an integer typedef there, so the clause
was already rejected.
The clause now only accepts `char` element types, which is what the spec
requires (OpenMP 5.1 §2.5.4: msg-string is a string of `const char *`
[5 lines not shown]
build/options: Remove old, obolsete GCC options
These aren't referenced in the tree anymore, so remove them from
here. This doesn't chanage src.conf.5, so I didn't commit that file.
Sponsored by: Netflix
www/ruby-aws-sdk-s3: update to 1.232.1
1.232.1 (2026-09-16)
* Issue - Return the copy response from multipart copy_to/copy_from instead
of nil on success.
www/ruby-aws-sdk-core: update to 3.257.0
3.257.0 (2026-09-14)
* Feature - Updated Aws::STS::Client with the latest API changes.
* Feature - Increases the maximum session token size to 4,096 bytes and
removes the packed policy size limit. Adds SessionTokenSize and
SessionTokenUtilization fields and a new MinimumSessionTokenSize
parameter. PackedPolicySize is deprecated.
databases/postgresql19-*: Update to 19.0-beta4
This release contains PostgreSQL 19 feature previews ahead of general
availability, though some details of the release can change during the
beta period.
The next planned release of PostgreSQL 19 is the release candidate,
which should occur in early October. Based on testing and evaluation,
this means that the PostgreSQL 19 GA may also occur in October. More
details will be provided as we move closer to these releases.
This beta release reverted several features that were originally planned
for PostgreSQL 19. The PostgreSQL community strongly believes that,
first and foremost, PostgreSQL must be reliable. Additionally, the
community strives for a predictable release schedule. Because of this,
the community chose to remove some features from the PostgreSQL 19
release so they can be potentially be included in a later major release
after more time working through the community development and review
process.
[2 lines not shown]
www/ruby-aws-partitions: update to 1.1289.0
1.1289.0 (2026-09-23)
* Feature - Added support for enumerating regions for
Aws::NetworkSecurityManager.
1.1288.0 (2026-09-22)
* Feature - Added support for enumerating regions for Aws::CloudWatchOmni.
[mlir][OpenACC] Preserve explicit device numbers in wait lowering (#222604)
WaitOpLowering currently ignores wait_devnum and always passes zero as
the device number to __tgt_acc_wait.
Forward the converted operand when present, adapting it to the runtime's
i32 parameter. Zero-extend narrow unsigned integers, sign-extend narrow
signed or signless integers, and truncate wider operands. Determine
signedness from the original operand type, since LLVM type conversion
makes integer types signless.
Keep the default device number unchanged when wait_devnum is absent.
Add regression coverage for explicit device numbers, integer width and
signedness conversions, index operands, and waits combining if and
async.