databases/mongodb70: fix build with clang 21
With clang 21 databases/mongodb70 fails to build, with errors similar to:
In file included from src/third_party/boost/libs/log/src/default_sink.cpp:20:
In file included from src/third_party/boost/boost/thread/locks.hpp:10:
In file included from src/third_party/boost/boost/thread/lock_algorithms.hpp:11:
In file included from src/third_party/boost/boost/thread/lock_types.hpp:18:
In file included from src/third_party/boost/boost/thread/thread_time.hpp:11:
In file included from src/third_party/boost/boost/date_time/posix_time/posix_time_types.hpp:16:
In file included from src/third_party/boost/boost/date_time/posix_time/posix_time_duration.hpp:15:
In file included from src/third_party/boost/boost/numeric/conversion/cast.hpp:33:
In file included from src/third_party/boost/boost/numeric/conversion/converter.hpp:13:
In file included from src/third_party/boost/boost/numeric/conversion/conversion_traits.hpp:13:
In file included from src/third_party/boost/boost/numeric/conversion/detail/conversion_traits.hpp:18:
In file included from src/third_party/boost/boost/numeric/conversion/detail/int_float_mixture.hpp:19:
In file included from src/third_party/boost/boost/mpl/integral_c.hpp:32:
src/third_party/boost/boost/mpl/aux_/integral_wrapper.hpp:62:51: error: in-class initializer for static data member is not a constant expression
62 | BOOST_STATIC_CONSTANT(AUX_WRAPPER_VALUE_TYPE, prior_value = BOOST_MPL_AUX_STATIC_CAST(AUX_WRAPPER_VALUE_TYPE, (N - 1)));
[23 lines not shown]
[AMDGPU] Ensure all PERMLANE instructions are marked as convergent (#182162)
All PERMLANE instructions in AMDGPUGenInstrInfo.inc were verified to now
be marked as convergent. This is necessary to prevent PERMLANE
instructions from being incorrectly sunk by machine-sink.
---------
Signed-off-by: John Lu <John.Lu at amd.com>
[LoopIdiomVectorize] Bail when vectorization is disabled (#181142)
Bail on vectorizing a loop in LoopIdiomVectorize when the loop carries
hints that indicate vectorization is disabled.
This means that LoopIdiomVectorize will now respect vectorize(disable)
loop hints.
NAS-139892 / 26.0.0-BETA.1 / Remove LEGACY_SHARE validation for path_suffix (#18251)
Prior to 25.10 we did not validate what users were putting as
a path_suffix in SMB shares that supported them. When the new
schema was added, a common path suffix type was used to limit
users to what is safe or makes sense.
Among specific items excluded were:
* Options that were under the client's control rather than
the server's control. Allowing clients to partially
dictate the share path can create an incorrect impression
of enhanced security because admin may not realize that
the client can change these.
* Options that often will break path creation or the ability
to auto-create ZFS datasets based on the naming schema
generated by the macro expansion.
This commit removes the path suffix validation from the
LEGACY_SHARE purpose, but keeps it for other ones.
tests: PortField: test well-known values against system #9835
Obsolete services have been removed which makes them error out.
Not sure if worth migrating or making the whole thing more clever.
Two appear to have been renamed.
AMDGPU/GlobalISel: Regbanklegalize rules for INTRIN_IMAGE (#179810)
Regbanklegalize rules for INTRIN_IMAGE loads and stores.
Because of very large number of different type signatures, rule specifies
only function for lowering (waterfall lowering of RsrcIdx operand if needed)
and this function also applies register banks.
[clang][Driver][Darwin] Turn on -gsimple-template-names for Darwin by default (#182297)
Enables `-gsimple-template-names=simple` when targeting recent Apple
platforms (26 or later, except `DriverKit` which is at 25). Those are
platforms where the associated LLDB is capable of debugging
`simple-template-names` debug-info.
The two main affects on debug-info are:
1. forward declarations for structures now have
`DW_TAG_type_template_parameter`s (since this is required to reconstruct
the template names if just given a forward declaration
2. `DW_AT_name` of templates will not include template parameters
anymore (except for a few cases where the name is not reconstitutible
from the template parameter DIE names)
While the `.debug_str` section is reduced in size (due to shorter
`DW_AT_name`s), this is somewhat offset by having to include template
parameter DIEs on forward declarations.
sysutils/dua-cli: update to 2.34.0
This upcoming release improves day-to-day usability with a new configuration file.
For users, the main additions are:
- A persistent configuration file for dua with keyboard settings under [keys].
- A new dua config edit command to open the configuration in $EDITOR.
- Automatic creation of the configuration directory/file with sensible defaults when editing for the first time.
Configuration defaults and behavior in this release:
- keys.esc_navigates_back now defaults to true. This is a change from previous versions where it was false implicitly.
You are welcome to contribute more settings as you see fit.
Chore
- Replace simplelog with fern and jiff for timestamped logging
- Note that this changes the log format from
04:41:37 [INFO] to [2026-02-06 05:41:32.146 +01:00 INFO src/main.rs:55]
[11 lines not shown]
Remove LEGACY_SHARE validation for path_suffix
Prior to 25.10 we did not validate what users were putting as
a path_suffix in SMB shares that supported them. When the new
schema was added, a common path suffix type was used to limit
users to what makes sense (excluding options that were
directly under the client's control since they can lead to
the incorrect understanding that shares are isolated from
each other in a way that enhances device security. The lack
of validation in LEGACY_SHARE for macro choices allowed users
to define path suffixes that produced undefined behavior
for shares. For example sometimes inserting invalid ZFS
characters into modules that should be auto-creating ZFS
datasets.
This commit removes the path suffix validation from the
LEGACY_SHARE purpose, but keeps it for other ones.
mvc: PortField: "wins" is known as "nameserver", sort list #9835
It makes sense to test all of these values in the unittest then
before this breaks during an OS update.
