[flang][NFC] Converted five tests from old lowering to new lowering (part 12) (#178831)
Tests converted from test/Lower: derived-pointer-components.f90,
derived-type-finalization.f90, derived-types.f90, do_loop.f90,
do_loop_unstructured.f90
tealdeer: update to 1.8.1
This patch release tweaks the enabled features for ureq, the library we
use to perform HTTP requests when updating the cache. In particular,
support for socks proxies is now enabled.
tor: Update to 0.4.8.22
Changes:
Changes in version 0.4.8.22 - 2026-01-28
This is likely the very last release of the 0.4.8.x series. Three major
bugfixes detailled below including two affecting directory servers (basically
all relays). We strongly recommend upgrading as soon as possible.
o Major bugfixes (security):
- Avoid an out-of-bounds read error that could occur with
V1-formatted cells. Fixes bug 41180; bugfix on 0.4.8.1-alpha. This
is tracked as TROVE-2025-016.
o Major bugfixes (directory servers):
- Allow old clients to fetch the consensus even if they use version
0 of the SENDME protocol. In mid 2025 we changed the required
minimum version of the "FlowCtrl" protocol to 1, meaning directory
caches hang up on clients that send a version 0 SENDME cell. Since
old clients were no longer able to retrieve the consensus, they
[42 lines not shown]
interfaces: host discovery: make sure the full dump includes NDP output if hostwatch is disabled
(cherry picked from commit f7fac5a6f4ac9ba502acab688a6d8092d942d77d)
pkg-vulnerabilities: restrict CVE-2021-39246 to older tor
This was fixed in tor-0.4.6.10 and should be no longer a problem given that v2
onion addresses should be no longer around and supported.
Pull up following revision(s) (requested by mrg in ticket #2001):
usr.sbin/ypserv/yppush/yppush.c: revision 1.26
_SC_OPEN_MAX can exceed FD_SETSIZE. Use the compat value svc_maxfd+1
from the rpc library similar to ypbind(8).
The custom _svc_run() function is required as the standard svc_run()
may hang for retries.
Fixes PR 59750.
Pull up following revision(s) (requested by mrg in ticket #1230):
usr.sbin/ypserv/yppush/yppush.c: revision 1.26
_SC_OPEN_MAX can exceed FD_SETSIZE. Use the compat value svc_maxfd+1
from the rpc library similar to ypbind(8).
The custom _svc_run() function is required as the standard svc_run()
may hang for retries.
Fixes PR 59750.
epair: add VLAN_HWTAGGING
Add capability VLAN_HWTAGGING to the epair interface and enable it by
default.
When sending a packet over a VLAN interface that uses an epair
interface, the flag M_VLANTAG and the ether_vtag (which contains the
VLAN ID and/or PCP) are set in the mbuf to inform the hardware that
the VLAN header has to be added. The sending epair end does not need
to actually add a VLAN header. It can just pass the mbuf with this
setting to the other epair end, which receives the packet. The
receiving epair end can just pass the mbuf with this setting to the
upper layer. Due to this setting, the upper layer believes that there
was a VLAN header that has been removed by the interface.
If the packet later leaves the host, the outgoing physical interface
can add the VLAN header in hardware if it supports VLAN_HWTAGGING.
If not, the implementation of Ethernet or bridge adds the VLAN header
in software.
Reviewed by: zlei, tuexen
[2 lines not shown]
Pull up following revision(s) (requested by mrg in ticket #168):
usr.sbin/ypserv/yppush/yppush.c: revision 1.26
_SC_OPEN_MAX can exceed FD_SETSIZE. Use the compat value svc_maxfd+1
from the rpc library similar to ypbind(8).
The custom _svc_run() function is required as the standard svc_run()
may hang for retries.
Fixes PR 59750.
ValueTracking: Revert noundef checks in computeKnownFPClass for fmul/fma (#178850)
This functionally reverts fd5cfcc41311c6287e9dc408b8aae499501660e1 and
35ce17b6f6ca5dd321af8e6763554b10824e4ac4.
This was correct and necessary, but is causing performance regressions
since isGuaranteedNotToBeUndef is apparently not smart enough to detect
through recurrences. Revert this for the release branch.
Also the test coverage was inadequate for the fma case, so add a new
case which changes with and without the check.
AMDGPU/GlobalISel: Regbanklegalize rules for G_UNMERGE_VALUES
Move G_UNMERGE_VALUES handling to AMDGPURegBankLegalizeRules.cpp.
Fix sgpr S16 unmerge by lowering using shift and using S32.
Previously sgpr S16 unmerge was selected using _lo16 and _hi16 subreg
indexes which are exclusive to vgpr register classes.
For remaing cases we do trivial mapping, assigns same reg bank
to all operands, vgpr or sgpr.
[lldb] Fix SBBreakpointName::SetEnabled to propagate changes to breakpoints (#178734)
When setting the enabled state of a breakpoint name via the API, the
change was not being propagated to breakpoints using that name.
This was inconsistent with the CLI behaviour where `breakpoint name
configure --enable/--disable` correctly updates all associated
breakpoints.
