amd64/ptrace-sce-tamper test: get rid of PT_TRACE_ME
PT_TRACE_ME is only useful in combination with exec and there is no
exec in this test.
Signed-off-by: Alex S <iwtcex at gmail.com>
MFC after: 1 week
EC2: Don't enable firstboot_pkgs in small flavour
The EC2 "base" flavour installs the devel/py-awscli package at boot
time by default; we don't do this in the "small" flavour, so the
default behaviour was to update the FreeBSD-ports repository and
then do nothing with it.
Turn off firstboot_pkgs by default; if someone is using the "small"
flavour of AMIs and wants to install packages at instance launch
time, they simply need to add 'firstboot_pkgs_enable="YES"' to
/etc/rc.conf (which they must already be editing via user-data, in
order to provide the list of packages they want installed).
Sponsored by: Amazon
MFC after: 3 days
MFC to: stable/15
Relnotes: EC2 "small" images now have firstboot_pkgs_enable="NO".
[LV] Update stale comment for partial reduction operands (NFC)
The `neg` form was removed in #187228 (this case now uses the out-of-loop sub, which is preferable, see #189739).
lang/python314: Update to 3.14.5
This release swaps out the incremental garbage collector for the
generational one used in 3.13 due to reports of memory pressure.
Backport the post-release upstream fix for:
Heap Buffer Overflow in pyexpat Character Data Buffering #148441
which is believed to be only triggered in rare circumstances.
Changelog: https://www.python.org/downloads/release/python-3145/
PR: 295200
MFH: 2026Q2
graphics/mesa-devel: drop hasvk driver after 790329e9a522
Old drivers are out of scope unlike mesa-dri. hasvk without userptr is
only useful for Vulkan on Intel Broadwell, anyway.
PR: 244877
[FileCheck][NFC] Introduce MarkerRange for -dump-input (#196800)
`MarkerRange` makes the computation of marker ranges clearer because it
encapsulates handling of several subtle boundary cases:
- It handles adjustments to line numbers when a range boundary appears
at a line boundary.
- It avoids related mistakes in determining whether the range is
contained within a single line.
- It avoids the mistake of producing no marker in an input annotation
for an empty range.
It will be used more in a future patch that extends `-dump-input` to
present search ranges for all errors.
This PR is stacked on PR #196799.
[AArch64][GlobalISel] Improve multiplication with multiple registers (#197943)
When working on codegen for `llvm.umul.fix.sat` I have recognized that
among for many things, GISel also generates worse code for mul when the
data is in multiple registers (for example when the register length is
64 bits but you want to multiply two 128 bit values).
Here is the example ll:
```
define i128 @i128(i128 %a, i128 %b) {
entry:
%s = mul i128 %a, %b
ret i128 %s
}
```
This is what GISel gave:
```
mul x9, x0, x3
[19 lines not shown]
