graphics/nvidia-drm-*-kmod: Add drm 6.12
Add new ports
graphics/nvidia-drm-612-kmod,
graphics/nvidia-drm-612-kmod-580 and
graphics/nvidia-drm-612-kmod-devel
and add conflicts to
graphics/nvidia-drm-{515|61|66|latest}-kmod{-580|-devel}
following the addition of graphics/drm-612-kmod.
While here, bump
graphics/nvidia-drm-latest-kmod,
graphics/nvidia-drm-latest-kmod-580 and
graphics/nvidia-drm-latest-kmod-devel
[13 lines not shown]
[clang] Add CLANG_USE_EXPERIMENTAL_CONST_INTERP cmake option (#199396)
To enable the new constant interpreter by default at configure time.
I don't expect any distributions to set this for now but it's useful for
testing and I think we need it eventually.
[lldb/test] Trim @expectedFailureAll(remote=True) decorators (#200529)
These three tests pass when run against a remote-darwin platform backed
by lldb-platform on device. Update each decorator to reflect where it's
still expected to fail rather than blanket-XFAILing every remote run.
- `TestAssertMessages.test_createTestTarget`: was XFAIL on
oslist=no_match(["linux"]) + remote=True. Add darwin_all to the no_match
list so the XFAIL stays only on remote-windows / remote-freebsd /
remote-netbsd / remote-android.
- `TestDebuggerAPI.test_CreateTarget_platform`: scope to non-Darwin
remotes (bug llvm/llvm-project#92419 still tracks the underlying issue
on those platforms).
- `TestObjcOptimized`: drop @expectedFailureAll(remote=True) from the
test method and put @skipUnlessDarwin on the class. The Makefile depends
on `-framework Foundation` and `-lobjc`, so the test cannot build on
non-Darwin platforms — skip it there outright instead of pretending it
could XFAIL.
Signed-off-by: Med Ismail Bennani <ismail at bennani.ma>
musescore: correctly report this as a "release" build
The exact CMake arguments had changed over time, and this was missed in
the update to 4.x.
While here, also drop another argument that has no effect. There is a
newer way of requesting the same, but we're not actually building that
way anyway at present, and enabling it leads to other troubles with Qt6
stuff.
[AMDGPU] Introduce ABI occupancy for object linking
This PR introduces ABI occupancy as the contract used to compile functions under
object linking. The default is derived from the occupancy needed for a 1024
workitem workgroup, can be overridden with `-amdgpu-abi-waves-per-eu`, and can
be overridden per function by `amdgpu-flat-work-group-size` or tightened by an
accepted `amdgpu-waves-per-eu` hint.
The backend emits the selected occupancy in `.amdgpu.info` and uses it to
enforce the object linking register budget.
edk2: enable static asserts for *INT64 alignment
The ia32 loader is now built with -malign-double, so these should pass.
Differential Revision: https://reviews.freebsd.org/D55386
stand: compile ia32 EFI loader with -malign-double
The UEFI spec says:
> Structures are aligned on boundaries equal to the largest internal
> datum of the structure and internal data are implicitly padded to
> achieve natural alignment.
Unlike the old Intel EFI toolkit, the EDK2 headers expect ia32 builds to
use -malign-double to achive this.
Make EFI versions of libsa32, liblua32, and ficl32. With the difference
being that they are compiled with -malign-double.
Differential Revision: https://reviews.freebsd.org/D55385
