[CodeGen][NewPM] Plumb MCContext through buildCodeGenPipeline
Otherwise we cannot create an MCStreamer without getting MMI, which we
cannot do until we have started running AsmPrinter without also plumbing
MMI through CodeGenPassBuilder.
Reviewers: arsenm, paperchalice, aeubanks
Pull Request: https://github.com/llvm/llvm-project/pull/182794
[NFCi][AsmPrinter] Refactor getting analyses to callbacks
As part of making AsmPrinter work with the new pass manager, we need to
be able to override how we get analyses. This patch does that by
refactoring getting all analyses/other related functionality to
callbacks that are set by default but can be overriden later (like by a
NewPM wrapper pass).
Reviewers: aeubanks
Pull Request: https://github.com/llvm/llvm-project/pull/182793
Revert "[ASan][Fuchsia] Have Fuchsia use a dynamic shadow start" (#182972)
Reverts llvm/llvm-project#180880
This is breaking Fuchsia's CI. something in the CMake needs to be
adjusted. Reverting on the author's request.
sysutils/amdmsrtweaker: fix build on recent FreeBSD
bmake has recently started to support $^ in addition to $>, causing
both to expand and leading to a build error like
c++ -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -Wall \
-Werror -pedantic -o amdmsrt Info.o AmdMsrTweaker.o WinRing0.o \
Worker.oInfo.o AmdMsrTweaker.o WinRing0.o Worker.o
c++: error: no such file or directory: 'Worker.oInfo.o'
Fix the error by avoiding both $^ and $>.
Approved by: portmgr (build fix blanket)
MFH: 2026Q1
net/ucx: Unified Communication X for high-performance messaging
UCX (Unified Communication X) is a high-performance communication framework
for modern HPC and data-intensive workloads. It provides low-latency,
high-bandwidth messaging and remote-memory-access primitives across a wide
range of transports, including shared memory, TCP/IP, and RDMA-capable
interconnects such as InfiniBand and RoCE (when supported by the platform).
UCX is commonly used as a communication substrate for MPI, OpenSHMEM, and
other distributed runtimes. It exposes a set of layered APIs (UCP/UCT/UCS/UCM)
to balance portability and performance while enabling optimized transport
selection, rendezvous protocols, and progress models.
PR: 292889
biology/ncbi-cxx-toolkit: only for aarch64, amd64
This port uses SIMD intrincis to compute CRC checksums.
It's probably easy to add a generic code path if desired.
Approved by: portmgr (build fix blanket)
MFH: 2026Q1
Sponsored by: Raptor Computing Systems, LLC
biology/ncbi-blast+: only for aarch64, amd64
This port uses SIMD intrincis to compute CRC checksums.
It's probably easy to add a generic code path if desired.
Approved by: portmgr (build fix blanket)
MFH: 2026Q1
Sponsored by: Raptor Computing Systems, LLC
biology/infernal: not for ppc64le
Project can use VMX, but only on big endian platforms.
Approved by: portmgr (build fix blanket)
MFH: 2026Q1
Sponsored by: Raptor Computing Systems, LLC
sysutils/symon: update to 2.90
- now broken on FreeBSD 15 on account of DIOCGETSTATUS being removed
Changelog: https://wpd.home.xs4all.nl/symon/changelog.html
Sponsored by: Raptor Computing Systems, LLC
textproc/regex2dfa: broken everywhere, very much out of date
/bin/sh ../../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I./../include -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -std=c++0x -MT fst.lo -MD -MP -MF .deps/fst.Tpo -c -o fst.lo fst.cc
libtool: compile: c++ -DHAVE_CONFIG_H -I./../include -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -std=c++0x -MT fst.lo -MD -MP -MF .deps/fst.Tpo -c fst.cc -o fst.o
In file included from fst.cc:26:
In file included from ./../include/fst/matcher-fst.h:26:
In file included from ./../include/fst/lookahead-matcher.h:28:
In file included from ./../include/fst/label-reachable.h:32:
In file included from ./../include/fst/accumulator.h:36:
In file included from ./../include/fst/replace.h:40:
In file included from ./../include/fst/state-table.h:31:
./../include/fst/bi-table.h:356:31: error: no member named 's_' in 'VectorHashBiTable<I, T, S, FP, H, HS>'
356 | : selector_(new S(table.s_)),
| ~~~~~ ^
1 error generated.
Upstream has since rewritten the whole thing in Python.
Perhaps an update is in order.
Approved by: portmgr (build fix blanket)
japanese/kdrill: fix build
This adds a missing parenthesis to $(LOCALBASE).
It is unclear why this hasn't been noticed earlier.
While we are at it, define LICENSE.
Fixes: 2546bd0290761071e3ad392427d7c2ba4e5a396b
Approved by: portmgr (build fix blanket)
MFH: 2026Q1
Sponsored by: Raptor Computing Systems, LLC
properly mask the "number of arguments" word to avoid invalid output.
i had a system soft-hang with cc1plus waiting for memory, but there
is enough memory free now, but when i tried to "bt/a <cc1plus addr>"
i was getting an extremely large output (several megabytes before i
killed simh).
we fetch the argument count from a 32-bit space in the stack frame,
but it's only the bottom byte that matters, the other bytes should
always be zero for netbsd, as they're used by VMS.
mask the high bytes of this value before consuming it.
also, since we don't expect to see them, simply give up when we find
a "callg" instruction. i did attempt to handle this, but since they
should not be present, and seeing one would indicate that an unexpected
stack write to that bit, handling it just leads to more faults as they
vax_ap pointer does not point to valid memory and triggers crash (ie,
back to db> prompt.)
properly mask the "number of arguments" word to avoid invalid output.
i had a system soft-hang with cc1plus waiting for memory, but there
is enough memory free now, but when i tried to "bt/a <cc1plus addr>"
i was getting an extremely large output (several megabytes before i
killed simh).
we fetch the argument count from a 32-bit space in the stack frame,
but it's only the bottom byte that matters, the other bytes should
always be zero for netbsd, as they're used by VMS.
mask the high bytes of this value before consuming it.
also, since we don't expect to see them, simply give up when we find
a "callg" instruction. i did attempt to handle this, but since they
should not be present, and seeing one would indicate that an unexpected
stack write to that bit, handling it just leads to more faults as they
vax_ap pointer does not point to valid memory and triggers crash (ie,
back to db> prompt.)
