new committer (src): Timothy Pearson (tpearson)
Complete steps 1-4 for new committers from the committer's guide:
1. Add myself to doc/shared/authors.adoc
2. Add myself to doc/shared/contrib-committers.adoc
3. Add a news entry
4. Add my PGP key
Approved by: jhibbits(mentor)
[MemoryBuiltins] Consider index type size when aggregating gep offsets (#132365)
[MemoryBuiltins] Consider index type size when aggregating gep offsets
Main goal here is to fix some bugs seen with LowerConstantIntrinsics
pass and the lowering of llvm.objectsize.
In ObjectSizeOffsetVisitor::computeImpl we are using an external
analysis together with stripAndAccumulateConstantOffsets. The idea
is to compute the Min/Max value of individual offsets within a GEP.
The bug solved here is that when doing the Min/Max comparisons the
external analysis wasn't considering the index type size (given by
the data layout), it was simply using the type from the IR. Since a
GEP is defined as sext/truncating indices we need to consider the
index type size in the external analysis.
This solves a regression (false ubsan warnings) seen after commit
https://github.com/llvm/llvm-project/commit/02b8ee281947f6cb39c7eb3c4bbba59322e9015b
(https://github.com/llvm/llvm-project/pull/117849).
Use the correct start address for the initial immutable address range
for a shared library. The code used the load offset of the shared
library instead of the start address of the mapped memory. In most case
that works because the first segment of a shared library typically starts
at virtual address zero. But on sparc64 (and possibly other architectures
that still use ld.bfd) libicudata.so from ports has a non-zero virtual
address (possibly because it is a data-only library). So this fixes
the bug reported by claudio@
ok deraadt@, jca@, claudio@
libpcap: Fix dependency definitions for libpcap
Commit 35dd53a9e132 ("librdmacm/libibverbs: Statically bound libbnxtre.so.1 to rping")
causes a build failure, since src.libnames.mk declares a depencency on
libbnxtre.so, but the libpcap Makefile and prebuild lib dependencies
were not updated accordingly. Fix the declarations.
Fixes: 35dd53a9e132 ("librdmacm/libibverbs: Statically bound libbnxtre.so.1 to rping")
Reviewed by: ssaxena
Differential Revision: https://reviews.freebsd.org/D54048
NAS-137051 / 26.04 / Increase setacl validation (#16910)
Raise a validation error if user submits ACL payload specifying a
username for a POSIX OTHER entry, NFSv4 everyone@ entry, or POSIX MASK
entry.
[Clang] adjust caret placement for the suggested attribute location for enum class (#168092)
Fixes #163224
---
This patch addresses the issue by correcting the caret insertion
location for attributes incorrectly positioned before an enum. The
location is now derived from the associated `EnumDecl`: for named enums,
the attribute is placed before the identifier, while for anonymous enum
definitions, it is placed before the opening brace, with a fallback to
the semicolon when no brace is present.
For example:
```cpp
[[nodiscard]] enum class E1 {};
```
[4 lines not shown]
py-geoip2: updated to 5.2.0
5.2.0 (2025-11-20)
* IMPORTANT: Python 3.10 or greater is required. If you are using an older
version, please use an earlier release.
* `maxminddb` has been upgraded to 3.0.0. This includes free-threading
support.
* Setuptools has been replaced with the uv build backend for building the
package.
* A new ``anonymizer`` object has been added to ``geoip2.models.Insights``.
This object is a ``geoip2.records.Anonymizer`` and contains the following
fields: ``confidence``, ``network_last_seen``, ``provider_name``,
``is_anonymous``, ``is_anonymous_vpn``, ``is_hosting_provider``,
``is_public_proxy``, ``is_residential_proxy``, and ``is_tor_exit_node``.
These provide information about VPN and proxy usage.
* A new ``ip_risk_snapshot`` property has been added to
``geoip2.records.Traits``. This is a float ranging from 0.01 to 99 that
represents the risk associated with the IP address. A higher score indicates
[5 lines not shown]
py-maxminddb: updated to 3.0.0
3.0.0 (2025-10-15)
* IMPORTANT: Python 3.10 or greater is required. If you are using an older
version, please use an earlier release.
* Databases can now be loaded from buffers. This can be done by passing in a
buffer as the database and using mode ``MODE_FD``. Pull request by Emanuel
Seemann.
* The C extension now supports Python 3.13+ free-threading mode and is
thread-safe for concurrent reads on platforms with pthread support (such as
Linux and macOS) and Windows. On other platforms, the extension will use
GIL-based protection.
* The C extension now uses PEP 489 multi-phase initialization, enabling
proper subinterpreter support and module isolation for Python 3.12+. This
modernizes the extension to use heap types instead of static types and
implements per-module state management. Key benefits include support for
Python 3.12+ isolated subinterpreters, multiple independent module
instances, and future-proofing for Python 3.14's InterpreterPoolExecutor.
[16 lines not shown]
This moves the code to lookup and set the pftable_id and rtlabel_id
from rde_apply_set() to filterset_recv(). This was already done in the
nexthop case.
OK tb@
