acpi: build dev/acpi_support/acpi_wmi_if.m on ARM64
Per Wikipedia, ACPI WMI support is available on all x86* platforms
and ARM platforms. Add the source to `files.arm64` so code that relies
on its headers (thunderbolt(4) for instance), can be built on ARM64.
MFC after: 1 month
Reviewed By: andrew
Differential Revision: https://reviews.freebsd.org/D55535
14.4/relnotes: Doc section is updated
Information about man page changes added,
man pages are sorted by section number, name.
Reviewed by: ziaee
Approved by: ziaee
Differential Revision: https://reviews.freebsd.org/D55618
[RISCV] Extends RISCVMoveMerger to merge GPRPairs independent of even/odd pair instruction order. (#183657)
This PR addresses post-commit reviews in #182416
Previously, `RISCVMoveMerger` only identified and merged 32-bit moves
into a 64-bit GPRPair move if the even-indexed register most appeared
before the odd-index register move.
This patch extends the pass by disregarding the order of even/odd-index
pair.
Remove CRYPTO options from man page
Since we do not build the code with CRYPTO defined, documenting
the CRYPTO options (pretending that they might work) in the man
page is misleading at best.
Rather than removing the text for the options completely, include
it conditioned on the C *roff number register being > 0 (and define
it to be 0 so the formatters don't format the CRYPTO sections of
the man page).
Add a comment to the Makefile indicating that if the commented
out section of it which would enable building with CRYPTO is
ever re-enabled, to also change the init of the C number register
in nc.1 from 0 to 1, so the options will return to the manual.
Clean up code, NFCI.
Add the /* $NetBSD$ */ header line, which wasn't added
when this was originally imported (NetBSD __RCSID was).
Move more of the CRYPTO related code into #ifdef CRYPTO
than was done before (global var decls, etc).
The -e option is CRYPTO related, does nothing without
the CRYPTO code, so move it out of the regular options,
retaining it only with CRYPTO.
The V option however (which was included with the CRYPTO
options in the getopts() arg string) is not CRYPTO related,
it is OpenBSD, and (when building for OpenBSD) would apply
to either CRYPTO or not. Fix that (though it makes no
difference when we exclude both CRYPTO & OpenBSD options).
Don't do run time tests that can never be relevant (like
[12 lines not shown]
In tzpath_ok(), also reject a path ending in "/..". This replaces
strstr() with a loop that matches "/../" in the name as well as
"/.." at the end. OK deraadt@
[OpenMP][clang] Indirect and Virtual function call mapping from host to device (#159857)
This patch implements the CodeGen logic for calling __llvm_omp_indirect_call_lookup
on the device when an indirect function call or a virtual function call is made
within an OpenMP target region.
---------
Co-authored-by: Youngsuk Kim
girara & zathura: update buildlinking to match current state
gitara had an SO major bump, so at minimum its ABI_DEPENDS needs
bumping. It also no longer requires GTK3, that moved to zathura, so
reflect it there instead.
No revbumps are needed, since all the dependent packages were updated
to new versions anyway. Ride those updates from earlier today.
shells/ksh-devel: Update to latest github commit plus additional fixes
Main changes:
- Removal of obsolete comments and build system workarounds.
- Update build/test command invocations.
- Add -j${MAKE_JOBS_NUMBER} flag to enable parallel building (I added
support for this last year).
- Ensure that ${SH} (/bin/sh) is used for shell actions while building.
- Install default shell functions in /usr/local/share/fun (for use with
FPATH and the autoload command). Symlink /usr/local/share/examples/ksh*
to that. (Of course you may decide to handle this differently, but it
would be good if the canonical share/fun directory were available.)
- Install the version with dynamic (*.so*) libraries by default (the STATIC
option can now be used to link those libraries statically). The version
with the libraries is preferred because this enables access to all the
libcmd built-ins (which are bound to /opt/ast/bin by default) and allows
writing C programs that link against these libraries -- you can even embed
the entire shell as a library. It would be good if this received wider
testing.
[5 lines not shown]
[AMDGPU] Insert readfirstlane for uniform VGPR arguments (#178198)
Fix inreg argument, which is uniform, but using VGPR due to run out of
SGPR.
---------
Co-authored-by: Matt Arsenault <Matthew.Arsenault at amd.com>
[HLSL] Add globals for resources embedded in structs
For each resource or resource array member of a struct declared
at global scope or inside a cbuffer, create an implicit global
variable of the same resource type. The variable name will be
derived from the struct instance name and the member name.
The new global is associated with the struct declaration using
a new attribute HLSLAssociatedResourceDeclAttr.
Closes #182988
math/octave-forge-mboct-fem-pkg: Premptive fix for GCC-15.
- Changes so that when GCC defaults to version 15, the port will
still build.
PR: 293334
Reported by: salvadore at freebsd.org
[mlir][acc] Add ACCRecipeMaterialization pass and reduction ops (#184252)
Pass
----
Add the `acc-recipe-materialization` pass, which materializes OpenACC
privatization, firstprivate and reduction recipes by inlining their
init, copy, combiner, and destroy regions into the operation for the
construct. The pass runs on acc.parallel, acc.serial, acc.kernels, and
acc.loop.
- Firstprivate: Inserts acc.firstprivate_map so the initial value is
available on the device, then clones the recipe init and copy regions
into the construct and replaces uses with the materialized alloca.
Optional destroy region is cloned before the region terminator.
- Private: Clones the recipe init region into the construct (at region
entry or at the loop op for acc.loop private). Replaces uses of the
recipe result with the materialized alloca. Optional destroy region is
cloned before the region terminator.
[42 lines not shown]
[Github] Respect LLVM_VERSION when building windows container (#184231)
Otherwise setting LLVM_VERSION does not actually do anything. This
avoids needing to update ~8 different locations in the file when doing a
toolchain bump to just 1 place.
[Github] Bump Github Runner to v2.332.0 (#184230)
To stay ahead of the support horizon. There were no major feature
changes/bug fixes from a cursory glance at the release notes.
