[lldb] Move dynamic type cache to common ABI runtime (#212014)
Both the Itanium and the MS ABI want some cache for dynamic types. This
moves the functionality from the Itanium ABI to the base class.
pfsync: handle large MTU pfsync interfaces
pfsync packets were allocated with m_get2(), which can't return packets
larger than MJUMPAGESIZE. As a result 9k MTU pfsync interfaces simply didn't work.
Use m_get3(), which can allocate sufficiently large mbufs.
Extend the pfsync:bulk test case to provoke this problem.
PR: 297307
MFC after: 2 weeks
Sponsored by: Rubicon Communications, LLC ("Netgate")
net: don't panic on ifconfig pfsync0 mtu 9000
pfsync interfaces do not have ifp->if_inet6 set, so when we update the
MTU for those interfaces we panicked.
Add an explicit check for this. This should be temporary, until pfsync
is no longer a struct ifnet (as we've already done for pflog).
Reviewed by: glebius
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D58701
Tools/scripts/update-plist.py: Updates pkg-plist
Small script using base Python to update pkg-plist based upon poudriere
error logs.
Inspired by: https://codeberg.org/tcberner/poudlist, by tcberner@. This
just uses base Python instead of C++ and flaky Boost libs, runs way
faster and requires no config file.
This is mainly intendend for simple ports and it's output should be
manually reviewed.
Disable NLS to ensure build consistency (and match the current PLIST)
This fixes the build when NLS is configured, because the PLIST does not
currently have any of the NLS files listed. If NLS is required for this
package, additional work will need to be done on the NLS option and
subsequent PLIST entries.
devel/cargo module: add MODCARGO_LIBTEST_ARGS variable
in order to pass arguments to LIBTEST (cargo test subsystem) and not to cargo
itself, provides a specific variable.
from Andrew Kloet (.net)
devel/cargo module: add MODCARGO_LIBTEST_ARGS variable
in order to pass arguments to LIBTEST (cargo test subsystem) and not to cargo
itself, provides a specific variable.
from Andrew Kloet (.net)
[IR] Set Number of Hungoff Uses after allocation (#213304)
If allocation of the Use[] in allocHungoffUses fails (e.g. due to OOM),
it may happen that the destructor of User is called with NumUserOperands
> 0. Then `Use::zap` tries to destruct Uses that were not constructed in
the first place.
Example scenario for SwitchInst:
`SwitchInst::init()` is called, which means the constructor of the
parent class User went through successfully, which means the destructor
of User will be called eventually. If now `SwitchInst::init()` calls
first `setNumHungOffUseOperands(2)` and then `allocHungoffUses()` and
the allocation there fails, `~User()` is called and tries to destruct 2
Uses, which can lead to problems.
This patch consequently ensures that first the allocation happens and
then NumUserOperands is set accordingly, so that this problem is
prevented.
