gecko: declare NOT_FOR_ARCHS=i386
The building and linking of the rust parts on x86 needs a larger
address space than a 32bit platform can provide (at most 4GB).
The gecko ports have been failing for quite a while on the official
builders with an "rustc-LLVM ERROR: out of memory" message, e.g.
https://pkg-status.freebsd.org/beefy18/data/144i386-default/6f1fe399c86f/logs/thunderbird-153.0.2.log
We can as well stop trying to save the CPU cycles leading up to
this error.
[SLP]Charge spill cost for loop-invariant gathers live over a call
Loop-invariant gathers hoisted to the preheader by
optimizeGatherSequence are live across calls in the loop body and need
spill/reload on targets with call-clobbered vector registers, but were
skipped by getSpillCost. Charge them like other call-crossing values.
Fixes #214555
Reviewers:
Pull Request: https://github.com/llvm/llvm-project/pull/215093
devel/isa-l_crypto: fix packaging on powerpc64le, enable powerpc64
Upstream 2.26 moved aes_cbc.h and aes_gcm.h into the AES module's
install list, and the AES module is only built on x86_64 and aarch64.
Other architectures use the generic base implementations, so the two
headers are not staged and check-plist fails. Gate them in pkg-plist.
powerpc64 builds the same generic code: both powerpc64 and powerpc64le
pass the upstream test suite (29/29, including the FIPS self-tests),
so widen ONLY_FOR_ARCHS.
Also correct ONLY_FOR_ARCHS_REASON: no isa-l_crypto release ever had
powerpc64le-specific code; all releases fall back to the generic C
implementations on ppc64*.
RuntimeLibcalls: Fix reporting incorrectly typed fp128 long double functions
l-suffixed long double math functions are fp128 only when the target's
long double is fp128. The default set provided them on every target that was
not x87 or ppc_fp128, so targets using double as long double wrongly reported
the fp128 l-suffixed functions.
Update tests that were reliant on phantom fp128 calls. These are only available
with glibc on select targets. In cases where the target supports the calls in
some triple, split the tests. In cases where the target has no fp128 library
support, delete the tests.
Co-authored-by: Claude (Claude-Opus-4.8) <noreply at anthropic.com>
www/nginx-acme: Update to 0.4.1
Fixes a possible crash during name resolution (via ngx 0.5.1).
https://github.com/nginx/nginx-acme/releases/tag/v0.4.1
While here, switch alignment to tabs (portfmt).
Sponsored by: Netzkommune GmbH
[ORC] Remove CallViaEPC.h and CallSPSViaEPC.h (#215086)
These provided EPC calls with pluggable serialization (EPCCaller /
EPCCall / SPSEPCCaller / SPSEPCCall). That role is now filled by the
RTBridge Proxy APIs (rt::Proxy + rt::sps::ProxySpec), and these headers
had no users other than their own unit test, so remove them along with
CallSPSViaEPCTest.
www/freenginx-acme-module: Add new port
ngx_http_acme_module adds automatic ACME (RFC 8555) certificate
management to freenginx. This port builds the module against the
stable www/freenginx and installs it into libexec/freenginx.
While here, move the freenginx version into www/freenginx/version.mk
(matching www/nginx and www/nginx-devel) so the new port can include
it as the single source of truth.
Sponsored by: Netzkommune GmbH
www/freenginx-acme-module: Add new port
ngx_http_acme_module adds automatic ACME (RFC 8555) certificate
management to freenginx. This port builds the module against the
stable www/freenginx and installs it into libexec/freenginx.
While here, move the freenginx version into www/freenginx/version.mk
(matching www/nginx and www/nginx-devel) so the new port can include
it as the single source of truth.
Sponsored by: Netzkommune GmbH
pci_iov: Use native types for status ioctl
IOV_CONFIG and IOV_GET_SCHEMA expose native pointers and size_t
lengths, and pci_iov has no compat32 ioctl translation. Using
fixed-width fields for IOV_GET_STATUS alone does not make the
interface usable by 32-bit binaries on a 64-bit kernel. It instead
complicates otherwise ordinary pointer and length handling.
Use void * and size_t like the existing ioctls. This also makes the
%zu diagnostic in iovctl correct on ILP32 and removes the unneeded
PTRIN conversion.
Fixes: 6f8b3be1fbd6 ("pci: Add SR-IOV status reporting")
pci_iov: Use native types for status ioctl
IOV_CONFIG and IOV_GET_SCHEMA expose native pointers and size_t
lengths, and pci_iov has no compat32 ioctl translation. Using
fixed-width fields for IOV_GET_STATUS alone does not make the
interface usable by 32-bit binaries on a 64-bit kernel. It instead
complicates otherwise ordinary pointer and length handling.
Use void * and size_t like the existing ioctls. This also makes the
%zu diagnostic in iovctl correct on ILP32 and removes the unneeded
PTRIN conversion.
Fixes: 6f8b3be1fbd6 ("pci: Add SR-IOV status reporting")
