[mlir][Affine] affine-super-vectorize transform op (#177755)
Added an operation in the transform dialect to apply the
affine-super-vectorize pass locally.
The operation vectorizes the loops that are children of the provided
operation, itself included.
Also added a test file verifying the operation behaves.
mail/mutt: Update to version 2.3.0
Changes since version 2.2.16:
+ $socket_receive_timeout and $socket_send_timeout cause mutt to
timeout on a network read/write operation, respectively. These
could be useful if you have an unreliable connection and
frequently find mutt gets stuck in a read.
! The folder browser now differentiates browsing for a file versus a
mailbox. For IMAP users, this means when attaching a file to an
email, mutt will browse your local computer by default.
! <edit-label> no longer untags messages. This is consistent with
other operations inside of mutt.
+ $imap_reconnect_tries and $imap_reconnect_sleep control the number
of times mutt will try to reconnect when a connection is lost, and
how long to sleep between each retry.
rust193: replicate openssl-sys patch for earlier versions, allowing build...
...for ilp32 NetBSD targets. Perhaps oddly, 32-bit arm succeeds without,
but neither does powerpc nor i386.
www/mozilla-firefox: Install a policy configuration file
mostly taken from https://justthebrowser.com/firefox/, Disables:
- Firefox Studies
- Checking if firefox is the default browser
- Sponsored stuff on the home page
- GenAI features
- PerplexityAI from the default search engines
in addition, frob GoToIntranetSiteForSingleWordEntryInAddressBar, which
forces firefox to ask your dns first if you enter a single word in the
address bar, useful to access local sites on your network instead of
sending your internal dns entries to $searchengine.
cf https://mozilla.github.io/policy-templates/#gotointranetsiteforsinglewordentryinaddressbar
many knobs to frob, but those seem to be a decent baseline to fight
against enshittification.
py-pyparsing: updated to 3.3.2
Version 3.3.2 - January, 2026
- Defined pyparsing-specific warning classes so that they can be selectively enabled
or disabled without affecting warnings raised by other libraries in the same Python
app:
- `PyparsingWarning` - base warning for all pyparsing-specific warnings (inherits
from `UserWarning`)
- `PyparsingDeprecationWarning` - warning for using deprecated features (inherits
from `PyparsingWarning` and `DeprecationWarning`)
- `PyparsingDiagnosticWarning` - warning raised when pyparsing diagnostics are
enabled and a diagnostic feature is used (inherits from `PyparsingWarning`)
- Added `as_datetime` parse action to `pyparsing.common` - a more generalized
version of the `convert_to_datetime` parse action (supports any expression that extracts
date/time fields into "year", "month", "day", etc. results names), and validates
that the parsed fields represent a valid date and time.
[15 lines not shown]
minizip-ng: updated to 4.1.0
4.1.0
Apply Clang format
align bzip and lzma streams for 64-bit platforms
Revert: Make pattern in mz_zip_reader dynamically assigned
Mark handle as unused.
doc: compression -> decompression
Updage usage of Buffered Stream
zstd: add MZ_STREAM_PROP_COMPRESS_THREADS
fix stack overrun in mz_os_utf8_string_create
harden mz_zip_writer_add_file against link following
refactor: passing reader, writer, zip instead of handle
zip_rw: validate the handle in each getter/setter
cmake: better zlib-ng / zlib handling
fix missing const at r/o buffers
Drop documents that are not freely distributable
Removing superfluous const
[9 lines not shown]
py-cucumber-expressions: updated to 18.1.0
18.1.0
Added
[Java] Add OSGi metadata
[Java] class KeyboardFriendlyDecimalFormatSymbols is now public and can be used when creating a custom Locale-aware type transformation method
Changed
[Ruby] Minor cosmetic / CI changes for development (Nothing front-facing)
[Python] PEP 639 licence metadata specification
Removed
[Python] Remove support for end-of-life Python 3.8 and 3.9
Make SHA aarch64 assembly build with gcc.
gcc is extremely fussy about register naming and insists on q and s naming
for the ARM CE SHA instructions, even though they're referring to the same
register (while LLVM just figures it out). Work around this by mapping
registers to their required variant at usage and defining a handful of
mappings between v registers and alternate names/views.
This is still somewhat ugly, but seems to be one of the cleaner options
that will allow portable to enable SHA assembly on platforms that use gcc.
ok kenjiro@ tb@
