MCContext/TargetMachine: Take MCRegisterInfo and MCSubtargetInfo by reference. NFC (#195032)
Both MCRegisterInfo and MCSubtargetInfo are non-null at every callsite
that matters (only nullable in unit tests like
`llvm/unittests/CodeGen/MFCommon.inc`), mirroring the recent `const
MCAsmInfo &` cleanup.
* TargetMachine::getMCRegisterInfo and getMCSubtargetInfo return
references.
* MCContext's constructor takes const MCRegisterInfo & and
const MCSubtargetInfo &.
[libc][math] Refactor rint-nearbyint family to header-only (#195577)
Refactors the rint-nearbyint math family to be header-only.
part of: #147386
Target Functions:
- nearbyint
- nearbyintbf16
- nearbyintf
- nearbyintf128
- nearbyintf16
- nearbyintl
- rint
- rintbf16
- rintf
- rintf128
- rintf16
- rintl
[4 lines not shown]
devel/vectorscan: disable FAT_RUNTIME on FreeBSD 14
The "fat" runtime build uses build_wrapper.sh to rename symbols via nm(1)
with the -f posix flag, which is not supported on FreeBSD 14.
Reported by: pkg-fallout
[flang][NFC] Converted more tests from old lowering to new lowering (part 55) (#195291)
Converted tests:
- Lower/Intrinsics/ieee_unordered.f90
- Lower/Intrinsics/rrspacing.f90
- Lower/structure-constructors.f90
- Lower/transformational-intrinsics.f90
Removed test:
- Transforms/stack-arrays.f90: tested the stack-arrays pass on the
legacy --array-value-copy output of legacy lowering. The HLFIR pipeline
produces fundamentally different code for array slice copies
(_FortranAAssign with fir.embox of sub-slices instead of allocating a
temp via array-value-copy), so the test's premises no longer apply. The
HLFIR equivalent test already exists at
Transforms/stack-arrays-hlfir.f90.
Partially revert previous to fix the builds.
The UVM stats functions are used (apparently) by the RUMP
"kernel", and need to be exposed as they were before, so
for now, do that.
Feel free to undo this, and fix the problem some other way.
[llubi] Add support for poison-generating/UB-implying annotations (#195339)
This patch adds support for poison-generating/UB-implying annotations,
including:
1. Parameter/retval attributes on function declarations and call sites
(range/nofpclass/align/nonnull/noundef/dereferenceable[_or_null]).
2. Metadata
(!range/!nofpclass/!align/!nonnull/!noundef/!dereferenceable[_or_null])
3. Assume operand bundles (nonnull/align/dereferenceable[_or_null])
I put all of them into a single patch as they share most of the common
logic.
Note that there are two todos to reach the full support:
1. Load with `!noundef` metadata doesn't check undef bits for now.
2. !dereferenceable[_or_null] on load (and inttoptr) are not tested by
this patch, as it needs the provenance support
(https://github.com/llvm/llvm-project/pull/185977). But it should be
fine as they are tested by metadata on call sites.
chinese/fcitx: Fix options GTK2 and GTK3, improve port
GTK2 and GTK3 options aren't working properly: even if disable GTK2, it
gets re-enabled GTK2.
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Fix warnings from portclippy.
- Set dependency from ecm as build.
- Convert CMAKE_ARGS to CMAKE_ON and CMAKE_OFF.
- Replace ".if ${PORT_OPTIONS:M***}" with new style options.
- Remove unnecessary KDE_MAN_PREFIX - it have default value.
- Remove description of Qt4 module from pkg-message.
- Use DESKTOPDIR in pkg-message.
PR: 294883
Approved by: lichray at gmail.com (maintainer)
Sponsored by: UNIS Labs
Co-authored-by: Ken DEGUCHI <kdeguchi at sz.tokoha-u.ac.jp>
[3 lines not shown]
chinese/fcitx: Fix options GTK2 and GTK3, improve port
GTK2 and GTK3 options aren't working properly: even if disable GTK2, it
gets re-enabled GTK2.
Improve port:
- Replace PORTVERSION with DISTVERSION.
- Fix warnings from portclippy.
- Set dependency from ecm as build.
- Convert CMAKE_ARGS to CMAKE_ON and CMAKE_OFF.
- Replace ".if ${PORT_OPTIONS:M***}" with new style options.
- Remove unnecessary KDE_MAN_PREFIX - it have default value.
- Remove description of Qt4 module from pkg-message.
- Use DESKTOPDIR in pkg-message.
PR: 294883
Approved by: lichray at gmail.com (maintainer)
Sponsored by: UNIS Labs
Co-authored-by: Ken DEGUCHI <kdeguchi at sz.tokoha-u.ac.jp>
MFH: 2026Q2
boot1.chrp: Specify --image-base
This is required for LLVM 22's ld.lld to avoid a build error:
ld.lld: error: section '.text' address (0x38000) is smaller than image base (0x10000000); specify --image-base
ld.lld: error: section '.rodata' address (0x3b308) is smaller than image base (0x10000000); specify --image-base
ld.lld: error: section '.data' address (0x3b610) is smaller than image base (0x10000000); specify --image-base
ld.lld: error: section '.bss' address (0x3f618) is smaller than image base (0x10000000); specify --image-base
Use 0x38000 for the image base, which is the address of the lowest
(and only) LOAD segment in the file.
Sponsored by: https://www.patreon.com/bsdivy
Differential Revision: https://reviews.freebsd.org/D56459
(cherry picked from commit aa0bc7cca153f67f8becec8a8fb259ff5fd30fd0)
libifconfig: Skip bridge VLAN config for span members
bridge(4) doesn't support BRDGGIFVLANSET for span members, which
means if a span interface is configured, libifconfig will fail to
fetch bridge members. Skip this for IFBIF_SPAN members.
PR: 292634
MFC after: 3 days
Reported by: Emrion <kmachine at free.fr>
Reviewed by: pouria, zlei
Sponsored by: https://www.patreon.com/bsdivy
Differential Revision: https://reviews.freebsd.org/D56694
(cherry picked from commit 454322c08b8aa181939c8d920472f03cfd591032)
[DirectX] Update error messages after #194061 (#195553)
Since DirectX is an experimental target these tests aren't failing on
public bots, but they obviously do when building DirectX.
[DirectX] Add missing test update for #191528 (#195552)
In #191528 we added the string table to the YAML and updated many tests
that were affected, but it looks like this one was missed.
nfsd: Disable use of callbacks for NFSv4.0
Commit 71ac1ec5c9d9 disabled callbacks for the NFS
client for NFSv4.0. This patch does the same for
the NFSv4.0 server.
The only use for callbacks for NFSv4.0 is delegations
and delegations rarely work well for NFSv4.0 anyhow.
Therefore, this patch disables callbacks for the
NFSv4.0 server. This is the same behavior as
occurs when vfs.nfsd.issue_delegations is 0.
This change allowed the functions called
nfsrv_getclientipaddr() and nfsrv_getipnumber() to be
removed from the kernel.
MFC after: 2 weeks
