[LV] Unify header phi fixup and remove fixNonInductionPHIs (NFC). (#204886)
Unify the execute logic for VPPhi and VPWidenPHIRecipe into a shared
executePhiRecipe helper that handles both scalar and vector phis. For
header phis, only the preheader incoming value is added during execute;
the backedge is fixed up later by VPlan::execute().
This allows generalizing the VPlan::execute() fixup loop to handle all
loop headers (not just the first), removing the VPWidenPHIRecipe skip,
and eliminating fixNonInductionPHIs entirely.
[Verifier] Verify AMX tile-register index operands are in range
AMX has 8 physical tile registers (TMM0-TMM7), so the tile-index operands
of the AMX intrinsics must be in [0, 8): operand 0 for the tile
load/store/zero intrinsics, operands 0-2 for the tdp* family.
imgact_elf.c indicate that interpreter is an interpreter
Use a value that do_execve will ignore since there's nothing there to do.
With this we can set the 'indirect' flag on rtld, to prevent direct execution
being used to bypass the 'indirect' flag on python3:
root at vuefi:~ # /libexec/ld-elf32.so.1 /usr/bin/python3 -c 'print("pwned")'
pwned
root at vuefi:~ # veriexec -z enforce
root at vuefi:~ # /libexec/ld-elf32.so.1 /usr/bin/python3 -c 'print("pwned")'
/libexec/ld-elf32.so.1: Operation not permitted.
root at vuefi:~ #
load_file seems missnamed since it is only used by load_interp
so rename it to load_interp_file.
Reviewed by: imp
Sponsored by: Hewlett Packard Enterprise Development LP
Differential Revision: https://reviews.freebsd.org/D57649
thunderbolt.4: Explain what driver does in manpage
Reviewed by: ziaee, ngie
Approved by: ziaee
Fixes: 2f7a796b590e ("thunderbolt.4: Initial manual for HW Relnotes")
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D57668
Update FreeBSD-EN-26:15.openssl.
There was a corrupted patch for FreeBSD-EN-26:15.openssl. Updating with
one that works correctly. Update the errata notice to reflect the
change. I am not intended to send an email for this update.
Reported by: dev at nicolas-provost.fr
Approved by: so
[AMDGPU] Use explicit carry nodes for i64 wide integer lowering
This PR switches widened i64 add/sub lowering to use explicit UADDO/USUBO carry
nodes instead of glue-based carry chains.
Import bind 9.20.24 (previous was 9.20.23)
Security Fixes
==============
Fix DNS64 owner case after DNAME restart. 4de2229364
When BIND 9 is configured to use DNS64 and encounters a DNAME redirect, it
could end up using freed memory for the DNS response owner name. This caused
the response to contain corrupted data. This fix ensures the correct owner
name is used when constructing the synthesized response after a DNAME
redirect.
ISC thanks Qifan Zhang of Palo Alto Networks for reporting the issue. [GL #5934]
New Features
============
Enable PR-Agent reviews on merge requests. 46e4c236a3
Adds a CI job that runs PR-Agent against each merge request opened from the
[143 lines not shown]
clang/AMDGPU: Remove driver restriction on --gpu-max-threads-per-block
Previously this flag was only handled for HIP, and would produce an unused
argument warning. There is a custom warning produced by cc1 that the
argument isn't supported, but practically speaking that was unreachable
due to not forwarding the argument. Also add a test for the untested warning.
Also use a simpler method for forwarding the flag to cc1.
jail: call PR_METHOD_ATTACH again (with old jail) if the first call fails
jail_attach lets modules do attachment-specific work by calling
osd_jail_call(PR_METHOD_ATTACH). If one of the modules returns an
error, the call needs to be repeated with the thread's current prison,
so possible earlier modules and undo any changes they may have made.
MFC after: 5 days
clang/AMDGPU: Remove driver restriction on --gpu-max-threads-per-block
Previously this flag was only handled for HIP, and would produce an unused
argument warning. There is a custom warning produced by cc1 that the
argument isn't supported, but practically speaking that was unreachable
due to not forwarding the argument. Also add a test for the untested warning.
Also use a simpler method for forwarding the flag to cc1.
clang/AMDGPU: Remove driver restriction on --gpu-max-threads-per-block
Previously this flag was only handled for HIP, and would produce an unused
argument warning. There is a custom warning produced by cc1 that the
argument isn't supported, but practically speaking that was unreachable
due to not forwarding the argument. Also add a test for the untested warning.
Also use a simpler method for forwarding the flag to cc1.
