NAS-140405 / 26.0.0-BETA.2 / Create S3 buckets before performing any restic operations (by themylogin) (#18574)
Restic retries errors for non-existing buckets. It retries them 10 times
with exponential backoff, so an operation on a non-existing bucket can
take several minutes to fail. There is no way to disable this.
Bucket existence checking and creation code was executed after running
`restic unlock`, resulting in very long operations, perceived as hangs.
Original PR: https://github.com/truenas/middleware/pull/18567
Co-authored-by: themylogin <themylogin at gmail.com>
NAS-140405 / 26.0.0-BETA.1 / Create S3 buckets before performing any restic operations (by themylogin) (#18573)
Restic retries errors for non-existing buckets. It retries them 10 times
with exponential backoff, so an operation on a non-existing bucket can
take several minutes to fail. There is no way to disable this.
Bucket existence checking and creation code was executed after running
`restic unlock`, resulting in very long operations, perceived as hangs.
Original PR: https://github.com/truenas/middleware/pull/18567
Co-authored-by: themylogin <themylogin at gmail.com>
[AMDGPU][GlobalISel] Add RegBankLegalize rules for permlane16_var/permlanex16_var (#187806)
Add register bank legalize rules for the amdgcn_permlane16_var and
amdgcn_permlanex16_var intrinsics. All register operands (result, old,
src0, src1) map to VGPR since these are VALU lane permutation
operations.
Enable -new-reg-bank-select in the permlane16.var test.
lang/ruby33: update to 3.3.11
Ruby 3.3.11 (2026-03-26)
From release announce:
This release includes an update to the zlib gem addressing CVE-2026-27820,
along with some bug fixes.
This is the last release of normal maintenance for the Ruby 3.3 series.
After this release, Ruby 3.3 enters a security maintenance phase. During
this phase, we will only backport security fixes and fixes for critical
build issues, without any regular bug fixes.
The security maintenance phase is scheduled to last for one year, until the
end of March 2027. At that point, official support for Ruby 3.3 will end.
We recommend that you begin planning your migration to Ruby 3.4 or 4.0.
Changes
[42 lines not shown]
[CodeView] Generate `S_DEFRANGE_REGISTER_REL_INDIR` (#187709)
In CodeView we had the limitation that we couldn't express locations
like `DW_OP_deref, DW_OP_plus_uconst 8` (i.e. indirect loads with an
offset). `S_DEFRANGE_REGISTER_REL_INDIR` allows us to represent this.
It's essentially `S_DEFRANGE_REGISTER_REL` (`Register + Offset`) with an
additional load afterward (`*(Register + Offset) + OffsetInUdt`).
These indirect locations are used in C++ 17 structured bindings and the
compiler generated C++ 20 coroutine stubs.
Before, locations that would only do a dereference without an added
offset afterward were represented by
`S_DEFRANGE_(REGISTER|FRAMEPOINTER)_REL` where the local had a reference
type:
```cpp
struct Foo {
int a;
[32 lines not shown]
NAS-140405 / 27.0.0-BETA.1 / Create S3 buckets before performing any restic operations (#18567)
Restic retries errors for non-existing buckets. It retries them 10 times
with exponential backoff, so an operation on a non-existing bucket can
take several minutes to fail. There is no way to disable this.
Bucket existence checking and creation code was executed after running
`restic unlock`, resulting in very long operations, perceived as hangs.
libfyaml: update to 0.9.6.
## [0.9.6] - 2026-03-15
### Major: Public Header Split
The monolithic `libfyaml.h` has been split into focused sub-headers under `include/libfyaml/`. The main header still exists and includes everything, so **existing code requires no changes**. Projects can now include only the sub-headers they need for faster compilation:
- `libfyaml/libfyaml-core.h` — parser, emitter, document, node, path
- `libfyaml/libfyaml-composer.h` — composer interface
- `libfyaml/libfyaml-docbuild.h` — document builder
- `libfyaml/libfyaml-allocator.h` — allocator API
- `libfyaml/libfyaml-atomics.h`, `libfyaml-thread.h`, `libfyaml-util.h`, and more
All gaps in the API documentation have been filled as part of this work.
### Added
- `fy_node_sequence_sort()`: Sort a single sequence node's items using a custom comparator (mirrors `fy_node_mapping_sort()`)
[44 lines not shown]
[HIP][CUDA] Apply protected visibility to kernels and globals (#187784)
Add the visibility override in setGlobalVisibility(), following the
existing OpenMP precedent. Unlike the AMDGPU post-hoc override, this
check respects explicit [[gnu::visibility("hidden")]] attributes
via isVisibilityExplicit().
libde265: update to 1.0.18.
1.0.18
libde265ConfigVersion.cmake renamed to libde265-config-version.cmake
fix pkg-config when installing to absolute paths
fix compilation with MSVC in Debug mode
removed the (defunct) encoder code and the internal development tools from the tarball
1.0.17
This release removes the autotools build scripts. Please migrate to cmake if you have not done that yet.
Furthermore, many input validations have been added and security relevant issues have been fixed.
CVE-2026-33165CVE-2026-33164
[LLVM] Replace use of LLVM_RUNTIMES_TARGET with LLVM_DEFAULT_TARGET_TRIPLE (#188303)
Summary:
This PR primarily changes using `LLVM_RUNTIMES_TARGET` to
`LLVM_DEFAULT_TARGET_TRIPLE`. The reason is that the default target
triple is the true cross-compiling architecture we are using, while the
runtimes_target can contain multilib strings like `+debug` or similar.
Additionally add the proper path handling to the OpenMP / Offload
libraries.
[flang-rt] Avoid duplicate definition of `std::__libcpp_verbose_abort` (#175551)
If a project depends on the Flang runtime and on libc++, linking fails
because `std::__libcpp_verbose_abort` is defined in both libraries.
Avoid that duplicate definition by defining `_LIBCPP_VERBOSE_ABORT`
before including any C++ headers and by renaming that symbol in the
Flang runtime to `flang_rt_verbose_abort`.
The function that is modified was originally introduced in D158957 to
solve an undefined symbol error when linking pure-Fortran projects with
the Flang runtime.
Providing a definition for that symbol in the Flang runtime might work
correctly for ELF or Mach-O if that symbol has weak linkage in libc++.
But at least for COFF, this now causes multiple-definition errors for
projects that are linking to the Flang runtime and to libc++.
The linker errors before this change for Windows/MinGW using
Clang+Flang+lld look like this:
[4 lines not shown]
